#1791 closed task (fixed)
Change DAE.RANGE type
| Reported by: | Martin Sjölund | Owned by: | somebody |
|---|---|---|---|
| Priority: | high | Milestone: | 1.16.0 |
| Component: | Frontend | Version: | |
| Keywords: | Cc: | Per Östlund, Peter Aronsson |
Description
Currently the type stored is not the full array type (Expression.typeof assumed the type of the range was this type; simplify and eval did not).
It should probably be changed to store the full type, so we can easily extract the dimensions from it (1:i to be DIM_EXP(i) instead of DIM_UNKNOWN(), etc).
Change History (11)
comment:1 by , 12 years ago
| Milestone: | 1.9.0 → 1.9.1 |
|---|
comment:2 by , 11 years ago
| Milestone: | 1.9.1 → 1.9.2 |
|---|
This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).
comment:3 by , 11 years ago
| Milestone: | 1.9.2 → 1.9.3 |
|---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:8 by , 9 years ago
| Milestone: | 1.11.0 → 1.12.0 |
|---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:9 by , 8 years ago
| Milestone: | 1.12.0 → Future |
|---|
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
comment:10 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I fixed this a while ago in 83e5e48.
comment:11 by , 5 years ago
| Milestone: | Future → 1.16.0 |
|---|
Postponed until 1.9.1