3 new lexer examples #284
Open
3 new lexer examples #284
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
First of all, thank you for your fantastic work on alex. I keep coming back to this repository.
I recently found myself needing more information from lexing errors, specifically error position in the input. I've been using the
basicwrapper, then switched toposnand finally landed onmonad. I had a difficult time putting together the full picture of an alex file implementing themonadwrapper and once I finally got it done, I thought my files could help somebody.Additionally, I made two small improvements/fixes so the examples compile with ghc 9.8.4:
import Data.Char (ord)required by examples:haskell.xtiger.xALEX=../dist-newstyle/build/x86_64-linux/ghc-9.8.4/alex-3.5.4.0/x/alex/build/alex/alex