| Age | Commit message (Collapse) | Author |
|
|
|
|
|
analysis intead of an integer. This is now consistent with lookupMorpho and friends
|
|
|
|
|
|
|
|
|
|
|
|
which generates the token
|
|
the parser in the Haskell runtime. This is also reflected in all bindings.
|
|
Haskell runtime
|
|
|
|
|
|
|
|
|
|
|
|
Python
|
|
instancein the lookup where the tokens produced from the metavariables are interpreted as distinct from all other tokens.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the Java binding
|
|
|
|
number of arguments to a function
|
|
|
|
|
|
|
|
|
|
|
|
longer a parameter to the callbacks.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The API in the C runtime as well as in the Haskell, Python and Java binding
is changed. Now instead of adding the literal callbacks to the concrete syntax
you need to supply them every time when you need to parse. The main reason is:
- referentially transparent API for Haskell
- when we start using memory mapped files we will not be allowed to change
anything in the grammar data structures. At that point the old API would
be impossible to use.
|
|
|
|
|
|
|