#4019 closed defect (fixed)
Using CombiTimeTable emits multiple unused variable tableAvailable warnings
| Reported by: | Owned by: | Martin Sjölund | |
|---|---|---|---|
| Priority: | high | Milestone: | 1.11.0 |
| Component: | Installation program | Version: | |
| Keywords: | Cc: |
Description
As soon as I use a Modelica.Blocks.Sources.CombiTimeTable, I get 5 warnings per used table, so e.g. loading several reference data files for a model severely diminishes the usefulness of the Messages Browser, as it just gets spammed with these messages.
This seems to be caused by m:#1138, so I guess it's improbable that the unused variable will be removed. To mitigate, can we at least silence/purge this specific warning instance, as it seems to "work as intended", and thus shouldn't generate a warning?
Repro code:
model unused_input_var Modelica.Blocks.Sources.CombiTimeTable test(table=[0, 0; 1, 0]); end unused_input_var;
Output:
[1] 15:13:57 Symbolic Warning [Modelica.Blocks.Sources: 2381:7-2382:66]: Unused input variable tableAvailable in function .Modelica.Blocks.Sources.CombiTimeTable$test.getNextTimeEvent. [2] 15:13:57 Symbolic Warning [Modelica.Blocks.Sources: 2346:7-2347:66]: Unused input variable tableAvailable in function .Modelica.Blocks.Sources.CombiTimeTable$test.getDerTableValue. [3] 15:13:57 Symbolic Warning [Modelica.Blocks.Sources: 2312:7-2313:66]: Unused input variable tableAvailable in function .Modelica.Blocks.Sources.CombiTimeTable$test.getTableValue. [4] 15:13:57 Symbolic Warning [Modelica.Blocks.Sources: 2358:7-2359:66]: Unused input variable tableAvailable in function .Modelica.Blocks.Sources.CombiTimeTable$test.getTableTimeTmin. [5] 15:13:57 Symbolic Warning [Modelica.Blocks.Sources: 2369:7-2370:66]: Unused input variable tableAvailable in function .Modelica.Blocks.Sources.CombiTimeTable$test.getTableTimeTmax.
Change History (6)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
| Component: | *unknown* → Installation program |
|---|---|
| Milestone: | Future → 1.11.0 |
| Owner: | changed from to |
| Status: | new → accepted |
comment:3 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
Should be fixed in OMLibraries/f20dc2c.
comment:5 by , 8 years ago
@sjoelund.se: sorry, I am still seeing this behaviour with the above repro model, using the recent OMEdit v1.11.0-dev-12-g3aded14, so apparently it's not fixed, or has the library patch not yet made it into a nightly?
These warnings are silenced for MSL 3.2.1, but in 3.2.2 new functions were added that I believe we do not patch.