On Sun, 2005-10-09 at 17:25 +0200, Yuval Kogman wrote: > Odd, I wonder why diagnosis are emitted on STDERR (or something else > maybe).
That's where Test::Builder emits them. Test::Harness never collected them or parsed them until recently. It's fairly difficult to decide whether a diagnostic is part of a specific test, so my guess is that writing them to a separate filehandle avoided that issue. > If they would go to STDOUT they would be visible by mouse-overing > the failing tests in Test::TAP::HTMLMatrix's output. > > Perhaps Parrot::Test is doing this change? If it is maybe it should > be changed via an env variable or something for the smokes? I think it would be useful in general, but it's not a guarantee that all of the information is useful or that any heuristic to identify the utility of any specific diagnostic would be correct. -- c
