balsoft/ligo
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
ligo/src/passes/01-parsing/pascaligo/.links

24 lines
491 B
Plaintext
Raw Normal View History

initial commit
2019-05-12 20:56:22 +00:00
$HOME/git/OCaml-build/Makefile
Integrated the library for preprocessing. The build with Makefile works. Dune build to be tested.
2020-03-31 19:44:10 +02:00
Gardening.
2019-10-07 16:33:34 +02:00
../shared/Lexer.mli
../shared/Lexer.mll
Finished refactoring of lexer.
2020-04-28 19:26:31 +02:00
../shared/LexerLib.mli
The preprocessor library depends now on the kinds of comments instead of a closed set of languages. I also removed the offsets: I simply use the current region to determine whether the preprocessing directie starts at the beginning of a line. I also removed scanning line indicators, to make the lexer simpler. LexToken.mll: Moved the function [check_right_context] that checks stylistic constraints from Lexer.mll to LexToken.mll. While this triplicates code (as CameLIGO, PascaLIGO and ReasonLIGO share the same constraints), the benefit is that Lexer.mll becomes more generic and the signature for the TOKEN module is simpler (no more exporting predicates, except for EOF). In accordance with the change of the preprocessor, the lexers and parsers for LIGO now depend on the kind of comments, not a fixed set of syntaxes. This gives more versatility when adding a new language: only the kinds of its comments are needed, although Lexer.mll and Preproc.mll may have to be modified if they do not already know the comment delimiters, for example line comments starting with #. **************************************************************** BUG: The exceptions coming from LexToken.mll when a stylistic constraint is broken in [LexToken.check_right_context] are not caught yet. **************************************************************** Lexer.mll: I moved out as much as I could from the header into a new module LexerLib. The aim is to make it easy to reuse as much as possible of the lexer machinerie, when it cannot be used as is.
2020-04-24 21:06:18 +02:00
../shared/LexerLib.ml
Gardening.
2019-10-07 16:33:34 +02:00
../shared/EvalOpt.ml
../shared/EvalOpt.mli
../shared/FQueue.ml
../shared/FQueue.mli
../shared/LexerLog.mli
../shared/LexerLog.ml
../shared/Markup.ml
../shared/Markup.mli
../shared/Utils.mli
../shared/Utils.ml
Sharing standalone lexers and parsers, and parser error API.
2020-01-04 19:49:22 +01:00
../shared/ParserAPI.mli
../shared/ParserAPI.ml
Refactoring of the front-end towards integration of the local builds and the globol build, using the parser error messages, for instance.
2020-01-23 18:28:04 +01:00
../shared/LexerUnit.mli
Sharing standalone lexers and parsers, and parser error API.
2020-01-04 19:49:22 +01:00
../shared/LexerUnit.ml
Additional refactoring to get local and global builds closer. I removed the last top-level effect (the execution of cpp). The idea is that ParserUnit.ml and each ParserMain.ml get closer to pascaligo.ml, cameligo.ml and reasonligo.ml, respectively.
2020-01-14 18:35:30 +01:00
../shared/ParserUnit.mli
Sharing standalone lexers and parsers, and parser error API.
2020-01-04 19:49:22 +01:00
../shared/ParserUnit.ml
The preprocessor library depends now on the kinds of comments instead of a closed set of languages. I also removed the offsets: I simply use the current region to determine whether the preprocessing directie starts at the beginning of a line. I also removed scanning line indicators, to make the lexer simpler. LexToken.mll: Moved the function [check_right_context] that checks stylistic constraints from Lexer.mll to LexToken.mll. While this triplicates code (as CameLIGO, PascaLIGO and ReasonLIGO share the same constraints), the benefit is that Lexer.mll becomes more generic and the signature for the TOKEN module is simpler (no more exporting predicates, except for EOF). In accordance with the change of the preprocessor, the lexers and parsers for LIGO now depend on the kind of comments, not a fixed set of syntaxes. This gives more versatility when adding a new language: only the kinds of its comments are needed, although Lexer.mll and Preproc.mll may have to be modified if they do not already know the comment delimiters, for example line comments starting with #. **************************************************************** BUG: The exceptions coming from LexToken.mll when a stylistic constraint is broken in [LexToken.check_right_context] are not caught yet. **************************************************************** Lexer.mll: I moved out as much as I could from the header into a new module LexerLib. The aim is to make it easy to reuse as much as possible of the lexer machinerie, when it cannot be used as is.
2020-04-24 21:06:18 +02:00
../shared/LexerLib.ml
Reference in New Issue Copy Permalink