Re: [tap] Valids subtests (was: RFC Status?)

[Andrew Rodland <[e-mail]>]

> A few notes on this.
>
> For subtests, they are indented four spaces. Always four spaces. If they are
> indented eight spaces, you know they're a subtest of a subtest (assuming
> there's an intervening subtest. That means this is valid TAP, but there is
> no subtest because it's indented too far:
>
> ok 1 - foo
>         ok 1 - bar indented too far
> ok 2 - bar passed
>
> The "ok 1 - bar" line would be discarded as "unknown".

I'm not trying to argue against established behavior, but I'd like to
point out that this disagrees with what you expressed in the previous
thread "More uncertainty about junk lines". In that, we agreed that it
was desirable that the determination of whether a line was
junk/unknown wasn't context sensitive. If it's potentially valid TAP
in any context, it's interpreted as that, and if that causes the TAP
document to be invalid, then so be it. If that holds true, then this
snippet is an error; it has a result in a subsubtest that lacks a plan
or a containing subtest.

Andrew