| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
function is linearizable in a given language. This is used in the Android UI for better vizualizations
|
|
|
|
created in a loop
|
|
header for alloca
|
|
|
|
|
|
|
|
|
|
|
|
support BIND. The following things are still broken: parseval, word completion, handling 'pre', the robust mode
|
|
|
|
PgfSymbolKS, PgfExprFun and PgfLiteralStr now keep their strings as embedded flexible arrays. The latest change gives us the same compactness as the old representation but it is a lot easier to use.
|
|
|
|
|
|
|
|
makes it easier to load grammars from the assets folder in Android
|
|
|
|
|
|
The old and broken Makefile is now removed
|
|
memory allocated in C.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and query for the list of languages
|
|
implementation for the binding
|
