----- Original Message ---- From: Joe McMahon <[EMAIL PROTECTED]> > Ovid, I currently need a good TAP parser, and I'm settling on yours > as *my* standard, anyway. It would seem futile to write yet another > one when I've got yours to work with. I will certainly put on my user > hat and start sending you "couldn't it just" mail as soon as > possible. :)
Thank you! That's exactly the sort of feedback I need. Also, if anyone can figure out why tprove_color fails with "Can't dup STDOUT" and tprove_color2 works, I'd be grateful. The former uses callbacks to cleanly output results and the latter is procedural (the former is somewhat procedural, bit I can't refactor until I can nail down the bug). I don't think there *should* be a reason why the former fails as the two are functionally equivalent. I'm wondering if it's some compile time thing as the former has the print statements wrapped in anonymous subroutines, but that doesn't seem right :/ Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
