Opened 13 years ago

Closed 3 years ago

Last modified 3 years ago

#1342 closed defect (fixed)

External functions should not be constant evaluated

Reported by: perost Owned by: perost
Priority: high Milestone: 1.16.0
Component: *unknown* Version:
Keywords: Cc: perost

Description

Modelica functions that call external code should not be constant evaluated, because we have no control over what side-effects they might cause.

Change History (4)

comment:1 Changed 13 years ago by sjoelund.se

Note: We now store a pure/impure attribute for functions. So this should be possible to implement (external functions should be impure by default, and a new annotation __OpenModelica_Pure = true could affect it; known pure functions (from MSL) should be part of the compiler).

comment:2 Changed 8 years ago by dietmarw

  • Cc changed from perost, to perost
  • Milestone set to Future

comment:3 Changed 3 years ago by perost

  • Component set to *unknown*
  • Resolution set to fixed
  • Status changed from new to closed

Fixed since the new frontend does not evaluate impure functions unless it's absolutely necessary.

comment:4 Changed 3 years ago by casella

  • Milestone changed from Future to 1.16.0
Note: See TracTickets for help on using tickets.