| Age | Commit message (Collapse) | Author |
|---|
|
|
|
ResolutionCallbacks.cpp
|
|
|
|
allow resolution for both
|
|
|
|
|
|
|
|
document graph
|
|
E.g. with regrads to the math ontology, this change allows syntax like
\(a^\frac{1}{2}\)
which is also valid in TeX (added corresponding tests).
|
|
resolution of referenced objects is still missing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
intra-document references.
|
|
|
|
until whitespace characters are reached. Improve tests accordingly.
|
|
reading data after the first whitespace character
|
|
|
|
|
|
|
|
|
|
correctly. Shorten Stack "checkTokensAreUnambiguous" method
|
|
|
|
needed. Reduces calls to "Manager.registerEvent" to <10% of original value
|
|
counting (though this change only has a small performance impact otherwise)
|
|
|
|
|
|
Idea: Only start unrolling anything on the parser stack
if an element that matches the given close token is found.
This requires the endToken method in DocumentChildHandler
to search for the given descriptor that might be ended.
While performing this search, only a specified number of
"explicit" structures/fields opened by the Stack class may
be skipped (those with implicit default fields).
Added an integration test ("python_code") which requires
this new (hopefully sane) behaviour.
|
|
"DocumentField" class
|
|
|
|
firstCharIsWhitespace methods for TokenizedData class
|
|
|
|
|
|
|
|
|
|
|
|
explicit fields.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
