Next: List of Well-formedness Checks, Up: Well-formedness [Contents][Index]
Well-formedness checks on the behavior
part of a model come in a
number of categories:
Interface, event and component definitions.
trigger
s and action
s are expected at different places
depending on the direction of their event
.
The imperative part of the language (assign
s, action
s,
function call
s) are only allowed in an imperative statement or in
a function body,
The use of statements within compound
s is restricted,
The usage of reply
,
The use of non-void
action
s and call
s,
The use of injected
ports,
A function body should be imperative, and have a well-defined return.
The use of data parameters,
The use of injected
ports,
All ports should be bound correctly.
Note: A trigger is an event that occurs and is prefixed by
on
in the behavior, an action is an event that is emitted inside the imperative body of a trigger.