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

Semantics of fixed initialization of clocked variable #3559

Open
henrikt-ma opened this issue Aug 12, 2024 · 2 comments
Open

Semantics of fixed initialization of clocked variable #3559

henrikt-ma opened this issue Aug 12, 2024 · 2 comments
Milestone

Comments

@henrikt-ma
Copy link
Collaborator

I find if odd that the chapter on synchronous features speaks nothing about pre(x) for a clocked variable, but still mandates that a clocked variable appearing inside previous(…) shall be treated as if it had fixed = true, which implies pre(x) = x.start during initialization. There is nothing obviously inconsistent about this, but it feels odd that the equation pre(x) = x.start seems more related to variables assigned in when-clauses than clocked semantics. Am I missing something, or is there something needing clarification?

@HansOlsson
Copy link
Collaborator

The entire initialization of clocked variables need to be worked on; currently there is no advanced initialization at all - but there is a proposal in MCP-0038.

@HansOlsson HansOlsson added this to the 2024-October milestone Oct 1, 2024
@HansOlsson
Copy link
Collaborator

See also #3577

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

No branches or pull requests

2 participants