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

Do we require a fixed memberName for high cut terminals? #209

Closed
klausschuch opened this issue Nov 19, 2024 · 1 comment · Fixed by #220
Closed

Do we require a fixed memberName for high cut terminals? #209

klausschuch opened this issue Nov 19, 2024 · 1 comment · Fixed by #220
Assignees
Labels
high-cut Describes an issue that concerns the high-cut
Milestone

Comments

@klausschuch
Copy link
Collaborator

The specification for the high cut currently says (4.4.2. Frame Terminal):

There must be one for the Clock this frame is connected to. The memberName of this variable must be "Clock".

Do we really need to have to require a specific memberName ("Clock") or wouldn't just the requirement that there has to be exactly one clock in this terminal be enough?
As far as I see this is the only fixed memberName that we require right now.

@chrbertsch
Copy link
Collaborator

Pierre: I would not require to have exactly one clock. We could need other clocks in the future. We should not require to name it "clock". Could we use variableKind? We could give it a special variableKind?
Klaus: currently it is variableKind="signal", this is perhaps not good.
Pierre: We could give it a specific variableKind

@bmenne-dspace bmenne-dspace added the high-cut Describes an issue that concerns the high-cut label Dec 6, 2024
@bmenne-dspace bmenne-dspace self-assigned this Dec 6, 2024
@bmenne-dspace bmenne-dspace added this to the 1.0.0-final milestone Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high-cut Describes an issue that concerns the high-cut
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants