ActivityMatch inherits privately from the EventMatch object, and is thus able to delegate relevant matching queries, but also to provide high-level special matchers. This new design resolves the ambiguity regarding function arguments. Moreover, we can now record the current sequence-Number as *attribute* in the respective log record (this is the benefit of using structured log entries instead of just a textual log), thereby avoiding the various pitfalls with explicit bracketing sequence-number log entries bottom line: this reworked design seems to be a better fit, even while technically the implementation with the wrapped matcher is somewhat ugly... |
||
|---|---|---|
| .. | ||
| diagnostic-output.hpp | ||
| event-log.cpp | ||
| event-log.hpp | ||
| microbenchmark.hpp | ||
| run.hpp | ||
| suite.cpp | ||
| suite.hpp | ||
| test-coll.hpp | ||
| test-helper.cpp | ||
| test-helper.hpp | ||
| test.h | ||
| testdummy.hpp | ||
| testoption.cpp | ||
| testoption.hpp | ||