(Oops. Accidentally sent this to Michael directly rather than to the list.)
--- Michael Peters <[EMAIL PROTECTED]> wrote: > I'm not sure I agree that there is a difference between them. They > are > both comments output by the tests. Just because one comes from the > testing routine used by the test and the other from the test itself > doesn't mean they aren't both just human readable comments on the > test run. is 3, 2, 'foo'; diag 'bar'; is 4, 5, 'baz'; If you run those tests, you know that (assuming we can get around the buffering problem) the lines beginning with "#" after the "not ok" line are the failure messages associated with a given test. Unfortunately, where "diag 'bar'" belong? Can we associate it with the first test or the second? There's no way of knowing what the programmer and you *can't* handle diag correctly if you can't disambiguate it. This is another reason why writing automated tools for TAP is problematic. There's more stuff folks would like to do and we need these issues resolved to make those things happen. Cheers, Ovid -- If this message is a response to a question on a mailing list, please send follow up questions to the list. Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
