Closed qlambert-pro closed 10 months ago
@HansOlsson can you suggest or add anyone else also for reviewing whom you think would be a subject matter expert , Thanks .
@HansOlsson can you suggest or add anyone else also for reviewing whom you think would be a subject matter expert , Thanks .
As far as I understand the library officers for Modelica.Blocks are @AHaumer and @MartinOtter but this isn't needing any special Blocks-competence.
Thanks @HansOlsson for clarifying . Let me add @hubertus65 for reviewing for the sake of merging (as it demands 2 reviewer's approval). Thankyou
Technically, these aren't forbidden as
table
is a parameter, andnoEvent
only matters if the operands are non-discrete-time expressions.However, that makes it confusing and redundant so it would be good to remove them.
I agree that it is confusing. Would it be desirable to get a warning when noEvent
is applied to a parameter expression? What about the more general case of noEvent(…)
not being a non-discrete-time expression?
Note from the MAP-LIB meeting: providing a warning about unnecessary and no-effect noEvent() operators is a quality of implementation issue. Warnings would be appreciated by modelers, but are not considered mandatory. 2023-11-14. Ticket is considered ready to merge.
According to Section 3.8.5 real elementary relations inside if-clauses controlled by a non-discrete-time switching expression are not allowed.