[tap-l] multi-file TAP

[Andy Armstrong]

On 7 Apr 2007, at 20:18, Ovid wrote:

> --- Andy Armstrong <andy at hexten.net> wrote:
>> plan 3
>> 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
>
> 1.  Your leading "plan 3" only had two begin/end sets.

And one top level test result for a total of three.

> 2.  I'd feel more comfortable if the "end" block also carried the
> description.

Yup, makes sense.

> 3.  Infinite TAP streams are allowed.  Infinite test files possibly
> should be allowed, also.

I think that's still OK, no?

>>> And with regard to BEGIN/END blocks, I don't think we need an END,
>
>>> just a BEGIN
>>> since we can treat it like Perl's "package" and just assume one
>>> file until we
>>> see another.
>
> There are non-perl folk on this list.  They might not know what
> BEGIN/END blocks are.  In any event, I'd still prefer to specify
> behavior rather than implementation.

More to the point they might not know what 'package' is. The BEGIN/ 
END being discussed here != Perl's BEGIN/END.

-- 
Andy Armstrong, hexten.net