Opened 11 years ago

Closed 4 years ago

#2703 closed defect (invalid)

Real den2[0,2] inside a function has an unknown type

Reported by: Adrian Pop Owned by: Martin Sjölund
Priority: high Milestone: Future
Component: Frontend Version: trunk
Keywords: Cc: Leonardo Laguna

Description

The function Modelica.Blocks.Continuous.Internal.Filter.base.CriticalDamping declares the following variable.

Real den2[0, 2];

That ends up having an 'unknown array' type while before it had 'real array'.

Change History (12)

comment:1 by Adrian Pop, 11 years ago

Cc: Leonardo Laguna added

comment:2 by Martin Sjölund, 10 years ago

Owner: changed from somebody to Martin Sjölund
Status: newaccepted

I get for generated code:

alloc_real_array(&_den2, 2, (modelica_integer) 0, (modelica_integer) 2);

Let me see if there is anything else weird for it.

comment:3 by Martin Sjölund, 10 years ago

OK, this will have to be closed if I don't get more information. The protected variable has type Real[0,2], and the use of that variable is simply {}.

comment:4 by Martin Sjölund, 10 years ago

Milestone: 1.9.11.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:5 by Martin Sjölund, 10 years ago

Milestone: 1.9.21.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:6 by Martin Sjölund, 9 years ago

Milestone: 1.9.31.9.4

Moved to new milestone 1.9.4

comment:7 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.5

Milestone pushed to 1.9.5

comment:8 by Martin Sjölund, 9 years ago

Milestone: 1.9.51.10.0

Milestone renamed

comment:9 by Martin Sjölund, 8 years ago

Milestone: 1.10.01.11.0

Ticket retargeted after milestone closed

comment:10 by Martin Sjölund, 8 years ago

Milestone: 1.11.01.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:11 by Francesco Casella, 7 years ago

Milestone: 1.12.0Future

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:12 by Per Östlund, 4 years ago

Resolution: invalid
Status: acceptedclosed
Note: See TracTickets for help on using tickets.