Re: [tap] Parse error vs failure

----- Original Message ----

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

> In Oslo, when we came across an edge case that was considered nonsense, the
> tendency was to say that its a parse error.  For example, "not ok 4 # SKIP",
> because why would you fail a test that didn't run?  Also "1..0" without a
> skip, because why would you not run any tests and yet not skip the test?

Your arguments made sense, but I have a question:  what does 'not ok 4 # SKIP' even mean?  To my mind, that's a parse error because something has gone horribly wrong or the person writing the TAP producer is terribly confused.  There's no way the parser can understand what the intent is, so making it a parse error makes sense to me because if *I* can't parse it, how can a TAP consumer?

I know I'm the odd man out here and I don't feel strongly enough about this to fight it :)

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
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap