Opened 9 years ago
Closed 3 years ago
#3727 closed defect (fixed)
Wrong output for model
Reported by: | Martin Sjölund | Owned by: | somebody |
---|---|---|---|
Priority: | high | Milestone: | 1.19.0 |
Component: | New Instantiation | Version: | v1.9.4-dev-nightly |
Keywords: | Cc: | Bernhard Thiele |
Description
The following model generates the wrong output for default --std=...
option:
model M Modelica.Blocks.Sources.Clock clock; annotation(uses(Modelica(version="trunk"))); end M;
It should generate an error that there is a conflict with the pre-defined class Clock, but it just instantiates the model as if it was a clock.
Change History (7)
comment:1 by , 9 years ago
comment:5 by , 8 years ago
Milestone: | 1.11.0 → 1.12.0 |
---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:6 by , 7 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:7 by , 3 years ago
Component: | Frontend → New Instantiation |
---|---|
Milestone: | Future → 1.19.0 |
Resolution: | → fixed |
Status: | new → closed |
Fixed in cd88b9e8, the model now compiles correctly regardless of --std
option (except that Modelica.Blocks.Sources.Clock
is now called Modelica.Blocks.Sources.ContinuousClock
in MSL 4.0.0).
Detecting an error would be correct, but the most practical thing (backwards compatible) would be if it would just instantiates
Modelica.Blocks.Sources.Clock clock
(ignoring that Clock is pre-defined).