Trent Nelson wrote:
What are your thoughts on this being included in your library?
Number one (including) is already present, at least in the INFO format. With an XInclude or external parsed entity-capable XML processor, it would also be present in the XML format. Neither JSON nor INI have include capabilities, and neither do any of the special sources, of course. However, it would be possible to write yet another parser for a format that has fancy include capabilities. Bottom line, including is a feature of the storage format and its parser, not the property tree itself. As for the second, value substitution, I think that should be an algorithm that you can apply to any tree. It will look up values of a special form and substitute them somehow. (By looking them up in the same tree, or perhaps by looking them up in another tree.)