-
Notifications
You must be signed in to change notification settings - Fork 21
WIP: Qualified fortran version #305
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
base: main
Are you sure you want to change the base?
WIP: Qualified fortran version #305
Conversation
bump singletons-* packages in order to build on recent ghc / cabal define unescapeSpecialChars in LexerUtils.hs use unescapeSpecialChars on the fail call, when the lexing aborts, which makes the output in the console more readable to end user
…ersion (either vanilla or qualified with options), and defining DecStructure CompilerOption. Done most of the plumbing to get the lexer compilation errors cleared and the new predicate, but hitting a stumbling block for now, on all the parser instantiations, higher order / curried symbols.
Ok, I succeeded in flowing the entry point options down to the parsers, now I'm facing some challenge to understand what I should do in the free form lexer, to support the In the fixed form lexer I see:
and the free form lexer:
fortran-src/src/Language/Fortran/Parser/Free/Lexer.x Lines 694 to 699 in b8a490f
I'm unsure how to proceed, when I've parsed I'd assume this flow:
What do those contexts mean: fortran-src/src/Language/Fortran/Parser/Monad.hs Lines 33 to 40 in b8a490f
I'll look more at this test and try to add one for free form: fortran-src/test/Language/Fortran/Parser/Fixed/LexerSpec.hs Lines 270 to 274 in b8a490f
|
…ouble with nested ones.
Wondering if we want to separate the QualifiedFortranVersion, which changes a bunch of signatures for the "already instanciated parsers" and the rest of the change I started working on (supporting option in QualifiedFortranVersion to parse the structure / record declarations in >= Fortran 90). |
I'm starting work to allow having
CompilerOption
list to describe the introducedQualifiedFortranVersion
, which will enable supportingDecStructure
option.Looking for maintainers feedback if this is right approach?
As of now, I'd like to get things to work back, which should be done by adjusting Parser.hs and maybe some more things in Main.hs, and later revise the new symbol names, which right now, may not be what we ultimately want.
If a maintainer want to look at the remaining type check error and suggest the right approach, as it is not clear to me at this stage.
Once this compile, I have a bit more work in the lexer to also have the
TRecord
token and maybe other things.todo:
[allocate]
.
field access in the lexerrelated: #303