| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
cleaner.
|
|
|
|
|
|
|
|
|
|
|
|
ParserState given the Type signature extracted from a ParserScope.
|
|
|
|
|
|
|
|
|
|
|
|
functions in ParserScope::resolve
|
|
first executes those resolutions that depend on not currently resolving nodes (this behaviour is needed for the resolution of constants).
|
|
|
|
|
|
already explicitly checked for).
|
|
|
|
|
|
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
|
|
reduces coupling and was stupid beforehand.
|
|
|
|
|
|
gave a ResourceManager instance to the Project, using ResourceRequest when including or linking files, thought through how "including" and "linking" are handled
|
|
be a better solution, e.g. to derive from ParserStack)
|
|
|
|
namespace, added new functionality to RegistryClass, wrote documentation, added function for extracting file extensions to Utils
|
|
|
|
|
|
|
|
a typesystem
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
