On 7/1/06, Yuval Kogman <[EMAIL PROTECTED]> wrote:
Another issue we had at work when I was abusing TAP for our C++ UT
framework was that we needed more levels of nesting (TAP only
supports streams and test cases - I was handling many test cases in
the same stream, for nested modules... I faked "files" on certain
markers, and used simple name mangling for the nestedness).
This is actually probably off topic, since TAP revisions are not
explicitly asked for... Too bad I missed talking to you at the
hackathon - if I had only thought about this we could have talked in
meat-space.
This sounds like the "test group" problem. Its known and we put
together a TAP extension at the BOF. I'll post that separately.
