[960] Fault unknown TAP tokens in strict mode (V13+)

[Eric Wilhelm]

# from Michael G Schwern
# on Saturday 16 February 2008 09:43:

>1) It allows old parsers to still understand a subset of new TAP.
>Making it dependent on the version helps with #1, I think.  I'd need
> some convincing this isn't backing us into a corner.

All new tap would have a known prefix?  That is, a v13+ parser should be 
able to say "that is a TAP keyword, but I don't support it."

>2) It allows one to test things that print to STDOUT.
>It doesn't solve #2.  One often doesn't have control over the code
> they're testing, so it makes that impossible.

Yes, something like system(wget ...), but where the command has 
no '--quiet' flag and the test is checking the side effect.  It would 
be a pain to have to wrap that sort of thing in IPC::Run.

Perhaps a 'begin/end noise' token of some sort?

I like the idea of TAP being stricter, but I'm not sure if it is 
warranted or desirable.

--Eric
-- 
Turns out the optimal technique is to put it in reverse and gun it.
--Steven Squyres (on challenges in interplanetary robot navigation)
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------