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 )
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")
In order to be able to include the .bin artifacts in a repository and craft releases / publish with cargo the sources may not be larger than 10MB or failures like:
error: api errors (status 200 OK): max upload size is: 10485760
will pop up.
The simplest path is to cache the compressed artifacts rather than the uncompressed and decompress at runtime. An optional builder A
Perhaps it should be opt-in, but most usage would expect a BOM is ignored.