| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
import detection.
|
|
|
|
|
|
|
|
|
|
|
|
functions in ParserScope::resolve
|
|
|
|
handling absolute paths in FileLocator for that.
|
|
first executes those resolutions that depend on not currently resolving nodes (this behaviour is needed for the resolution of constants).
|
|
|
|
|
|
and GuardedLogger
|
|
|
|
|
|
|
|
|
|
finished yet.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
already explicitly checked for).
|
|
|
|
|
|
|
|
supposed to be called)
|
|
|
|
|
|
description to "reference*" to have a consistent nomenclature
|
|
|
|
|
|
complete yet. also improved output path handling.
|
|
|
|
|
|
ParserScope in order to store data that should be available between parser instances, but cannot be stored in the object graph.
|
|
ill-defined -- if a parser only parses a partial document via include, there may be many to no nodes that are returned). Parsers should just use the ParserScope.push funciton. All nodes pushed onto the top-level of the ParserScope are added treated as the nodes the parser has parsed. Adapted all code and all tests accordingly.
|
|
|
|
ParserScope and using it in the Manager
|
|
an object reference or pointer as the Logger class
|
|
|
|
|
|
reduces coupling and was stupid beforehand.
|
|
type is used within a stl container)
|
|
options).
|
|
|
