omc accepts undefined identifiers in structural varying models

[Christoph Höger]

model IfExpression
  parameter Boolean b = true;
  Integer i = if not b then c else 1;
equation
  assert(i == 1, "The value of i must be 1");
end IfExpression;

The above model should fail (and there should be a testcase to catch that error).

See: ​m:#1101#comment:5
I suppose it is because of some inlining/constant folding, as the result looks like this:

class IfExpression
  parameter Boolean b = true;
  Integer i = 1;
equation
  assert(i == 1,"The value of i must be 1");
end IfExpression;

omc should certainly do typechecking _before_ evaluation ;).

[Martin Sjölund]

I have actually worked on this in the past, and see #1736 for a similar issue. Silly old libraries and other things :(

[Martin Sjölund]

Postponed until 1.9.1

[Martin Sjölund]

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).

[Martin Sjölund]

Milestone changed to 1.9.3 since 1.9.2 was released.

[Martin Sjölund]

Moved to new milestone 1.9.4

[Martin Sjölund]

Milestone pushed to 1.9.5

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Ticket retargeted after milestone closed

[Martin Sjölund]

Milestone moved to 1.12.0 due to 1.11.0 already being released.

[Francesco Casella]

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.

[Per Östlund]

This gives an error as expected when using the new frontend, since it instantiates the whole model before doing type checking and simplifying if-expressions.