A grammar describes the syntax of a programming language, and might be defined in Backus-Naur form (BNF). A lexer performs lexical analysis, turning text into tokens. A parser takes tokens and builds a data structure like an abstract syntax tree (AST). The parser is concerned with context: does the sequence of tokens fit the grammar? A compiler is a combined lexer and parser, built for a specific grammar.
The rust code in the .lalrpop files are still on rust 2015 and need to be manually updated since cargo fix won't work on those files.
We should also update the generated code to emit 2018 idiomatic code (see #2018 )
Tokenizer.pipe, Rules.suggest and maybe some other methods should return an iterator instead of a Vec<_> for more flexibility.
I'm using link-grammar-5.3.15.
This one didn't work for me:
https://github.com/opencog/link-grammar/blob/master/bindings/java/org/linkgrammar/LinkGrammar.java#L43
Even when I added /usr/local/lib to jvm props:
java.lang.UnsatisfiedLinkError: no liblink-grammar in java.library.path
I fixed it by replacing that line into:
System.load("/usr/local/lib/liblink-grammar-java.so")
It would be great to see a tutorial on how to port a pyparsing based project to Lark.