Actually I arried at the conclusion, that the *receiving* of a diff representation is actually a typical double-dispatch situation. This leads to the attempt to come up with a specialised visitor as standard pattern to handle and apply a diff. Obviously, we do not want the classical GoF-Visitor, but (yes, we had that discussion allready) -- well in terms of runtime cost, we have to deal with at least two indirections anyway; so now I'm exploring the idea to implement one of these indirections through a functor object, which at the same time acts as "Tag" in the diff representation language (instead of using an enum as tag) |
||
|---|---|---|
| .. | ||
| time | ||
| diagnostic-context-test.cpp | ||
| DIR_INFO | ||
| streamtypebasicstest.cpp | ||
| streamtypelifecycletest.cpp | ||
| teststreamtypes.hpp | ||
| typed-counter-test.cpp | ||
| visitingtool-concept.cpp | ||
| visitingtool-extended-test.cpp | ||
| visitingtool-test.cpp | ||