This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Can XDC Proxy declarations occur in config files for executables?



I have a custom interface module which I now need to integrate with some other code which has not been RTSC modularlized. Rather than forcing that code into a module, could a proxy be declared at the cfg file level?

Thanks

  • If I understand the question correctly, you have an interface IMod and some code that implements the functions from the interface, but there is no a formal declaration in an XDC file about that hierarchy? Then, you would want to use that code where an IMod implementation is expected. Is that correct?

    I don't think there is a way to make it work. One of the purposes of XDC files is to establish types, and then when you run a config script, every assignment to a config parameter is type-checked. In the case described above, there is no a typed object to assign to a config parameter that expects a module that inherits IMod.

    You could probably develop a facade module that forwards all calls to the existing code, without chaging anything in the existing code. I don't have an example of it on hand, but if you decide to try it I could help you with some inevitable glitches you'll find along the way. 

  • I've implemented a facade module, and the integration and testing are currently underway.