Opened 10 years ago
Closed 10 years ago
#2832 closed defect (fixed)
Annotation in external objects is lost when instantiating
Reported by: | Owned by: | Martin Sjölund | |
---|---|---|---|
Priority: | high | Milestone: | 1.9.1 |
Component: | Frontend | Version: | trunk |
Keywords: | Cc: |
Description (last modified by )
When instantiating an external object, the annotation in the class is lost. It seems to me like it would be present in the DAE.ElementSource in the DAE.EXTOBJECTCLASS, but InstFunction.instantiateExternalObject fills in very little information in the source for a DAE.EXTOBJECTCLASS.
To be clear, it is the annotation commented as X below that is missing.
class Model extends ExternalObject; function constructor .... end constructor; function destructor ... end destructor; annotation(...); // X end Model;
Change History (4)
comment:1 by , 10 years ago
comment:3 by , 10 years ago
Description: | modified (diff) |
---|---|
Milestone: | → 1.9.1 |
Owner: | changed from | to
Status: | new → accepted |
comment:4 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
This should work in r22454, but OpenModelica does not use the annotations on the class so I cannot test it.
Note:
See TracTickets
for help on using tickets.
Which annotations that affect code generation do you believe the compiler should be able to access for external objects (and do not belong in the constructor/destructor)?