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

Allow a user to define their own signal names. #35

Open
jrbeaumont opened this issue Aug 8, 2016 · 1 comment
Open

Allow a user to define their own signal names. #35

jrbeaumont opened this issue Aug 8, 2016 · 1 comment

Comments

@jrbeaumont
Copy link
Member

Currently, because we do not store names for signals when defining concepts, we find the number of signals in the system and name them from A.

All signals are also defined as outputs, so being able to define signals as inputs, outputs and internal will reduce a step post-translation.

@jrbeaumont
Copy link
Member Author

Signal types is discussed in issue #17.
This issue has been renamed to simply be based on signal names.

@jrbeaumont jrbeaumont changed the title Allow a user to define their own signal names and types. Allow a user to define their own signal names. Aug 22, 2016
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

1 participant