-
Notifications
You must be signed in to change notification settings - Fork 8
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
✨ Jump Tables #26
base: main
Are you sure you want to change the base?
✨ Jump Tables #26
Conversation
I don't think It seems the purpose of the feature is to allow you to define offsets from a tablestart. But the offsets have to be declared in a separate place from the only place they can be used. It seems redundant. |
@@ -0,0 +1,19 @@ | |||
#define macro MAIN() = takes(0) returns(0) { | |||
ANOTHER() | |||
asterix: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you used dests instead of offsets, this can be allowed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Has nothing to do with that, could allow it regardless, just a choice I made to have tables be more explicit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The table is already explicit enough I think; it doesn't need to be limited
I somewhat agree, however right now I just want to replicate the features |
No description provided.