[tap-l] What's with verbose rewriting the TAP?

[Ovid]

----- Original Message ----

> From: Michael G Schwern <schwern at pobox.com>

> I've just noticed another instance of "prove -v" rewriting the TAP so that
> you're not really seeing what the test output.

Mea culpa.  I did that when I first wrote TAP::Parser to ensure a nice, consistent output showing the end-user what TAP::Parser is interpreting each TAP line as.

So yeah, I could see this being an issue.  Should we have --raw to show the original TAP?  Or --normalize to show what TAP::Parser is intending?  I think Schwern is right that we should show the actual output by default.  (/me wonders if this will break any tools relying on the new parser)

 
And Schwern, is there a bug in your mail software?  Here's the to: line from the headers:

  To: Development at a-sasl-fastnet.sasl.smtp.pobox.com,
     of at a-sasl-fastnet.sasl.smtp.pobox.com,
    "TAPx:"@a-sasl-fastnet.sasl.smtp.pobox.com:Parser <tapx-dev at hexten.net>

Cheers,
Ovid
--
Buy the book         - http://www.oreilly.com/catalog/perlhks/
Tech blog            - http://use.perl.org/~Ovid/journal/
Twitter              - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6