| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
for compatibility with older versions of GHC
|
|
the parser in the Haskell runtime. This is also reflected in all bindings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Haskell runtime
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the callbacks. It is just as easy to save the sentence in a closure and by doing that we save the repeated round about from C to Haskell strings
|
|
incorrect since they encode the string in the system locale while the C runtime is always using UTF8
|
|
|
|
|
|
|
|
finding an abstract tree whose linearization matches given keywords
|
|
|
|
literal expressions
|
|
|
|
semantic graph
|
|
|
|
|
|
abstract&parse trees
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
loading grammars compiled with -split-pgf
|