#2400 closed defect (fixed)
Values.RECORD cannot represent records
| Reported by: | Martin Sjölund | Owned by: | Martin Sjölund |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.9.0 |
| Component: | Frontend | Version: | trunk |
| Keywords: | Cc: | openmodelicadevelopers@…, Peter Aronsson, Leonardo Laguna |
Description
Values.RECORD contains only a list of names and values. But in order to convert a value to expression, we need to remove protected variables since they do should not be passed to the record.
This affects Modelica.Electrical.Spice3.Examples.Nor (which for some reason compiles using gcc anyway; probably it thinks the empty argument to the list means varargs). Regardless, it needs to be fixed.
Change History (6)
comment:1 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 11 years ago
| Cc: | added |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
comment:3 by , 11 years ago
In which cases will code like
Complex(<expression>,<expression>)
be interpreted as a DAE.CALL to the Complex constructor and which cases will it be interpreted as a DAE.RECORD?
comment:4 by , 11 years ago
Currently, anything translated from Values.RECORD back will be using a DAE.RECORD. In the future, I aim to remove DAE.CALL to the constructor function (and the constructor function itself) from the DAE since it does not really work like a normal function.
Fixed in r17553, but note that the changes made since DAE.mo changed! Code generation needs to be updated, etc.