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 not include COMMENT and DEFINE statements in executable statement list #12

Open
sixlettervariables opened this issue Nov 12, 2015 · 0 comments

Comments

@sixlettervariables
Copy link
Owner

Place these in their own properties on the result from the parser.

sixlettervariables added a commit that referenced this issue Nov 12, 2015
- Implements #11 through properties for executable statements, labels,
comment references, and image definitions.
- Implements #12 by only including executable statements in the
`statements` property (BREAKING CHANGE)
- Implements #13 by allowing an options argument to be sent to the
parser. If the options argument contains a level definition, the
restrictions encoded in it will be used during parsing to produce
compile time errors.
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