Adam Kennedy wrote:
> chromatic wrote:
>> On Monday 17 April 2006 18:50, Ovid wrote:
>>
>>> The only problem I see with that is the occasional buffering errors I
>>> see on my Mac where the STDERR and STDOUT don't line up.
>>
>> Agreed.  Is it too late to send everything to STDOUT where it belongs?
> 
> Unfortunately, it probably is too late.
> 
> Schwern made one small change in the STDERR format, and the recursive
> cascade of failing test-testing modules hit something like 3000 CPAN
> distributions.

While I agree that this caused problems, those modules were relying on a
format that was not spec'ed out or documented.

In fact, the TAP spec explicitly says that diagnostics can/should be
mixed with test output. At least to me, that means they're on the same
output stream.

http://search.cpan.org/~petdance/Test-Harness-2.56/lib/Test/Harness/TAP.pod#Diagnostics

> Changing TAP without extreme caution, planning and co-ordination could
> get be very very nasty, especially out there in the darkpan.

I do agree that caution and coordination is necessary. It's the test
modules themselves (Test::More, etc) that print to STDOUT/STDERR, right?
 And there sure are a lot of them. If I had any TAP producing test
modules on CPAN I'd volunteer to change them :)

-- 
Michael Peters
Developer
Plus Three, LP

Reply via email to