parser: support regex style begin-end anchors (^, $)
#723
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These are the only anchors supported by Hyperscan, making it easier to write handler patterns that should match exclusively at the beginning or at the end of a stream. The exception mapping has also been changed in `hexstring2regex`, as anchors are processed during lexing, and it raises a different exception then what is raised during parsing. Fortunately lark has a nice exception base class to use.
vlaci
force-pushed
the
hexstring-anchors
branch
from
811a311 to
86a90c4
Compare
qkaiser
approved these changes
Jan 25, 2024
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are the only anchors supported by Hyperscan, making it easier to write handler patterns that should match exclusively at the beginning or at the end of a stream.
The exception mapping has also been changed in
hexstring2regex, as anchors are processed during lexing, and it raises a different exception then what is raised during parsing. Fortunately lark has a nice exception base class to use.