----- Original Message ---- From: Ovid <[EMAIL PROTECTED]> > If Test::Builder accepted an environment variable which allowed > me to override this, I might have a way out. So far removing the > 2>&1 seems to make my tests pass on a Linux box, but that > strikes me as bizarre as I thought STDERR wouldn't get read > that way. What the heck am I misunderstanding?
OK, now I know what the problem is. I wasn't thinking clearly :( Basically, in reading perlopentut, I don't see any way of portably capturing both STDOUT and STDERR, much less keeping them in synch. The reason my tests worked is that the regression tests put everything in STDOUT and my other tests didn't cover the case of STDERR and STDOUT being separate streams. Thus, TAPx::Parser seems to be almost dead in the water for much of what I was hoping to accomplish. Is there some other option? Schwern, I know you initially showed that redirecting STDERR to STDOUT causes no diagnostic information to appear, but that's only in the case of Test::Harness, yes? Would you accept a patch which allowed this redirection so that other TAP parsers have a chance of overcoming this limitation? Again, am I missing something fundamental here? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
