Experiment: make GAP scanner/reader accessible from GAP #4130
+409
−17
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This experimental PR is something I've been telling people for a long time now; since I never seem to find time to clean it up and finish it, I thought I should post it here as-is; perhaps it motivates someone to join forces or to do their own thing.
This patch adds a way to take any input and run it through the parser, but without executing it, or printing any syntax errors etc. Instead the tokens as found by the scanner are recorded in a plain list, as is information about syntax errors.
To try it out, compile it, then
ReadLib("tokenizer.g");
This has numerous potential application
Test
could be written, in pure GAP (I don't see any reason to do that right now, I just mention it)Of course to get there, more work should be done. For one, this proof of concept should be polished and turned into something nicer: