the rationale is that I deliberately do not want to provide a mechanism to iterate "over all contents in stringified form". Because this could be seen as an invitation to process GenNode- datastructures in an imperative way. Please recall we do not want that. Users shall either *match* contents (using a visitor), or they are required to know the type of the contents beforehand. Both cases favour structural and type based programming over dynamic run-time based inspection of contents The actual task prompting me to add this iteration mechanism is that I want to build a diagnostic, which allows to verify that a binding message was sent over the bus with some specific parameter values. |
||
|---|---|---|
| .. | ||
| diff-language.hpp | ||
| diff.cpp | ||
| gen-node.cpp | ||
| gen-node.hpp | ||
| index-table.hpp | ||
| list-diff-application.hpp | ||
| list-diff-detector.hpp | ||
| list-diff.hpp | ||
| record-content-mutator.hpp | ||
| record.hpp | ||
| tree-diff-application.hpp | ||
| tree-diff.hpp | ||
| tree-mutator.hpp | ||