Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call blocks in response language #9

Closed
HeikoKlare opened this issue Sep 22, 2016 · 1 comment
Closed

Call blocks in response language #9

HeikoKlare opened this issue Sep 22, 2016 · 1 comment
Assignees

Comments

@HeikoKlare
Copy link
Contributor

Currently, explicit routines can be called anywhere in the execution block of any other routine.
This can be confusing because in correspondences added in the calling routine are not yet added to the correspondence model when executing the called routine although the add operation was defined above the execution block.

To make clear what assumptions can be made when calling another routine, we should add an explicit call block at the end of a response/routine in which other routines can be called and for which it is obvious that the rest of the response/routine was already completely executed.

@HeikoKlare
Copy link
Contributor Author

Arising from #13, we should allow the call of other routines anywhere in the effects, but as an explicit statement rather than within the generic execute block like before. Due to the changed (timing) semantics of the individual statements in the effects block, no unexpected behavior can occur because the statements are then executed in the order in which they are defined.

Consequently, call blocks should be definable anywhere in the effects as a first level statement:

effect: {
    ...
    call: doSomething(...)
    ...
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant