Changes between Version 1 and Version 2 of Ticket #3772, comment 1


Ignore:
Timestamp:
2016-03-17T10:18:39Z (9 years ago)
Author:
Rüdiger Franke

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3772, comment 1

    v1 v2  
    1 The runtime code generation calls
    21See #3752
    32
    43Both the C and the Cpp templates currently call the frontend function Expression.getClockInterval. It returns 0.0 for an unknown (inferred) clock.
    54
    6 The runtime code generation should introduce a default clock i #3752.
     5The runtime code generation should introduce a default clock in #3752.
    76
    87Here we have an event clock, for which Expression.getClockInterval returns 0.0 too. The runtime code generation must treat the event clock in that case.