[tap-l] multi-file TAP

[Andy Armstrong]

On 7 Apr 2007, at 21:01, Eric Wilhelm wrote:

> # from Andy Armstrong
> # on Saturday 07 April 2007 08:58 am:
>
>> plan 4
>> begin "Spigot extraction"
>>    plan 3
>>    ok 1 Spigot::Extractor loaded
>>    ok 2 Spigot visble
>>    not ok 3 Spigot free
>> end
>> begin "Documentation"
>>    plan 1
>>    ok 1 Documentation makes sense
>> end
>> ok 3 All tests completed
>
> Doesn't that last line invalidate the 'plan 4' bit?

It should be plan 3 - two begin/end pairs and a naked test.

> If we're indenting, couldn't we do without the 'end'?

I'm only indenting for clarity. I suppose that - for even more  
clarity - I could have mentioned that :)

> Even without indenting, I'm a bit wary of a begin/end scheme simply
> because it allows results and files the same status.  It's like a data
> structure of:

[snip]

> Maybe I'm just suffering the xml jitters.  Even the above scares me.
> It's like we're going to build a data structure using only the tag
> <node>.

Well programming languages manage OK with only a single <node> tag,  
often called '{':

  statement ::= simple-statement
            |   '{' simple-statement * '}'

Here's a problem: how to we handle TAP version? You'd want the TAP  
version at the front of a TAP stream to reflect the version of  
everything the stream contains - but if you're merging multiple  
streams you haven't necessarily seen them yet to know what version  
they are.

-- 
Andy Armstrong, hexten.net