
david at kineticode
Aug 11, 2008, 9:57 AM
Post #7 of 7
(1085 views)
Permalink
|
On Aug 10, 2008, at 21:25, Ashley wrote: > On Aug 10, 2008, at 8:50 PM, David E. Wheeler wrote: >> On Aug 10, 2008, at 12:51, Jonathan Rockway wrote: >>>>> Remind me why this is better? >>>> >>>> It prevents the output from fucking up the harness. >>> >>> I don't think the harness looks for anything on STDERR. >> >> `diag` sends stuff to STDERR. So yes, it does. > > Is that true? I don't know the suite well but a casual peek at > Test::Builder's guts looks like it goes to STDERR and STDOUT > alternately depending on whether the output was from failure or from > intentional calls. I think the reason it never interferes with test > harness is that the output is escaped/#commented. Right. Which is why I suggest `diag` instead of `warn`. Best, David _______________________________________________ Catalyst-dev mailing list Catalyst-dev[at]lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev
|