Multiple implementation: language ID vs folder name
The folder name for an implementation may not be exactly the name of the language. We need a mapping for example Simulink is SIMULINK (upper case)
These are the folder names:
Concrete example:
- I create a function with a default implementation set to "Simulink"
- taste will create a folder named /SIMULINK (uppercase) to store the implementation
- we add an implementation in the IV (e.g. in C)
- Space Creator will try to move /Simulink in the implem subfolder... Because it does not know the name is SIMULINK, not Simulink.
So in the list of languages, I think you have to add an attribute "folder_name" (to be filled by me) and use it instead of the raw language name
Edited by Guenter Schwann