Jerome Hugues
Jerome Hugues
Bug solved, see commit in this issue
Yes, you are right, that would simplify the codebase
Subsequent work required to homogenize the processing of multi-languages subprograms - [ ] check that Source_Text and Source_Language match - [ ] reduce code duplication
I did a first pass at supporting this feature. Remaining actions - complete property resolution in AST (analyser part) - revisit instantiation mechanism
Similar patch must now be adapted for other drivers, this will be down as part of their update
Actually, this change would need to be propagated to other drivers, reopening
[Note: The nice thing with the OSATE plug-in is that it uses the property sets of OSATE in place of the ones provided by Ocarina. To test with Ocarina without...
This patch solves (or hides) this issue. It appears one needs to revisit the way we process properties that are records. This is the major task to be done for...
An initial support has been implemented, I now need to implement proper entity resolution. Will be done when time permits
Ocarina embeds both parser all the time ocarina -aadlv2 -> use v2 parser ocarina -aadlv1 -> use v1 parser ./configure --aadlv2 -> v2 parser default, no need to add -aadlv2...