Group A Issues

Discussion

Avigail proposed that we always use the clock context of the place where the endpoint is used - this implies that we must be able to infer a clock from the modeling layer (or pass in a clock parameter, or include the clock explicitly in the endpoint declaration).

Resolution

1. Default clock definitions apply only to directives with no top-level clock. (No change to the current LRM definition.)
2. An instance of an unclocked endpoint declaration will inherit the clock context that applies at the location of the endpoint instance.
3. Any occurrence of built-in function rose, fell, or prev will inherit the clock context that applies at the location of that occurrence.
4. For each built-in function that is sensitive to the clock context (prev, rose, fell [and also stable]), add an optional Boolean parameter representing a clock expression.

Additional Notes

• did not intend to define a clock context for the modeling layer
• Cindy mentioned a related issue regarding definition of clocks (see email)

LRM Changes

• First Draft
• Second Draft
• Third Draft
• Fourth Draft
• Default Clock Declaration proposal