Hi all, I've just started hacking together TAP::Diagnostics. This would be a simple helper module that allows test authors to spit out the YAMLish diagnostics envisioned for future versions of TAP. I have some specific ideas on how to make this work, but we need to agree on the format. For ideas:
http://testanything.org/wiki/index.php/TAP_diagnostic_syntax If we can't come to a consensus, I'll plow ahead regardless. As usual, this means I might create something that no one likes. What I'd prefer to define is the *minimum* required keys in the YAML diagnostics and perhaps an optional set of *may have* keys (which might be optionally enabled for deeper debugging). Minimum required: wanted found line file description I think that's a decent minimal set of required keys. Is this OK with everyone? Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Perl and CGI - http://users.easystreet.com/ovid/cgi_course/ Personal blog - http://publius-ovidius.livejournal.com/ Tech blog - http://use.perl.org/~Ovid/journal/
