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

Add syntax and semantics to mark output ports as required #260

Open
bocchino opened this issue Jun 8, 2023 · 0 comments
Open

Add syntax and semantics to mark output ports as required #260

bocchino opened this issue Jun 8, 2023 · 0 comments
Labels
proposed feature A proposed new feature

Comments

@bocchino
Copy link
Collaborator

bocchino commented Jun 8, 2023

Motivation: Sometimes port connections are required for a topology to make sense, e.g., a handler invokes an output port which, if unconnected, causes FSW assertion failure. Other times port connections are not required, e.g., a handler checks whether an output port is connected before invoking it.

Proposal: A port specifier in components can optionally be required, e.g.,

active component C {
  ...
  required output port p: P
  ...
}

In this case it is a topology error to instantiate component C to an instance I and leave port I.p unconnected.

@bocchino bocchino added the proposed feature A proposed new feature label Jun 8, 2023
@bocchino bocchino changed the title Add syntax and semantics to mark ports as required Add syntax and semantics to mark output ports as required Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposed feature A proposed new feature
Projects
None yet
Development

No branches or pull requests

1 participant