# from Michael G Schwern
# on Tuesday 27 January 2009 18:16:
>For example, if a test program knows that it is going to
>exit abnormally, even after it has finished emitting TAP according to
> its plan, it should emit one final "not ok" line before exiting.
So,
1. TAP::Harness should store that
chromatic wrote:
> On Friday 23 January 2009 20:48:57 Michael G Schwern wrote:
>
>> But these days a TAP parser can catch most premature exits by just looking
>> at the exit code of the test, so the plan is less useful than it once was.
>
> That assumes that the TAP parser has some degree of cont
David Cantrell wrote:
> On Sat, Jan 24, 2009 at 12:16:33AM +0800, Gaurav Vaidya wrote:
>
>> Based on the recent questions on the TAP mailing list asking about the
>> significance of "1..", I wonder if this could be simplified to:
>> TAP version 13
>> 1..2 # Initialization
>> ok 1
