--- Steffen Schwigon <[EMAIL PROTECTED]> wrote: > Now, what, in your example, are the keys you want to > standardize/reserve for tap specific purposes? IMHO all keys (file, > line, results, have, want, name, display) are specific to > Test::Differences. You probably don't want to standardize them, or do > you?
OK, I think I may have misunderstood something. None of those keys are specific to Test::Differences. Consider: is 3, 2, "say it ain't so"; That outputs something like: not ok 1 - say it ain't so # Failed test 'say it ain't so' # at t/foo.t line 23. # got: '3' # expected: '2' As you can see, we still have file, line, results, have, want, name and display, but in an unstructured form (display is almost useless here, but it can be quite useful in many other contexts). > I think it's quite rare to have keys that are really specific to TAP > (not to TAP producers). The specific keys mentioned above will likely be very common. It's already fairly straightforward to capture the file and line, but the rest is waiting on Test::Builder 2. 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/
