On Wednesday 07 March 2007 11:39, Eric Hacker wrote: > Now if all TAP can handle is Perl, or even just code output, then > those of us pushing the envelope will eventually migrate to some other > test output format.
TAP can certainly handle more than just Perl and code output. In my mind, the questions are: 1) Do existing TAP features already provide this feature? 2) Do existing TAP features almost already provide this feature, with a little bit of work? 3) Is this a feature that TAP should support somehow? 4) Is this generalizable to different domains? 5) Is there a clean way to add this to TAP while retaining backwards compatibility? I'm still not sure what you're doing that requires anything other than a machine-parsable diagnostic, but I have a failure of imagination sometimes. -- c
