Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upRemove then/begin/end tokens. #161
Conversation
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
I'm pretty sure that was indeed a lazy attempt. I vaguely recall thinking the lexer would reject * because it would match earlier as just a '*', but of course that's not true. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Fyren commentedNov 7, 2017
Currently, you can use
*beginand*endto enclose compound statements in a lot of places as well as use*thento not require parentheses around the test forifstatements. I have no idea why they have asterisks in the first place. Perhaps a lazy attempt to remove the syntax?This patch additionally removes the ability to do
while a == 1 do stmt();.