| Age | Commit message (Collapse) | Author |
|---|
|
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).
|
|
|
|
-> this causes these operations whenever the top-level scope instance is destroyed, which is the last possible point at which deferred resolution can take place. Validation must come after deferred resolution.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
be parsed
|
|
|
|
make no sense.
|
|
|
|
|
|
|
|
gave a ResourceManager instance to the Project, using ResourceRequest when including or linking files, thought through how "including" and "linking" are handled
|
|
|
|
|
|
class and corresponding (unfinished) test
|
|
|
|
|
|
|
|
|
|
|
|
|
|
compatible with the Variant cardinality.
|
|
reading tests.
|
|
|
|
|
|
|
|
|
|
for cardinalities.
|
|
|
|
|
|
isOpenLow, isOpenHigh)
|
|
|
|
will forever be a mess, but it is PREEEEETYYYY!)
|
|
|
|
|
