On Tue, Aug 19, 2008 at 3:11 PM, David Golden <[EMAIL PROTECTED]> wrote: > On Tue, Aug 19, 2008 at 8:02 AM, Gabor Szabo <[EMAIL PROTECTED]> wrote: >> Sure. IMHO that is what *diag* is for. >> To print all kinds of messages to the screen in a TAP. > > Going up the thread, I think you had asked about whether the harness > could catch warnings to find things that T::NW can't. I think I was > pointing out that there are legitimate reasons for a test author to > issue "warnings" -- diag is just a specially formatted warning, after > all. So I don't think the harness can be expected to distinguish > warnings from code versus intentional "warnings" from the test only > from observing the output stream.
Sure people can fake the output of diag. For now I'd like someone to start reporting anything not in the TAP stream. Then, if someone really wants to do it, she can replace the diag to be silent and catch anything which looks like coming from diag that obviously was only faking it. Gabor
