Justin Mason wrote:
2. In that config-parse callback, define and register an eval rule
*on the fly*, once the rule is parsed:
This isn't appropriate for my rule types. I don't want to iterate over
each possible rule definition, I want to do lookups in hash tables.
sounds like a meta subrule: __FOO_baz. Or am I missing something?
Unlike subrules, I want the hit to be included in the list returned by
PerMsgStatus::get_names_of_tests_hit(). The whole purpose of FOO_baz is
to be visible, making diagnosis easier.
