On 8 Apr 2007, at 02:07, Fergal Daly wrote:
begin
begin
ok
end
begin
not ok
end
end
Yes, I said it was nestable but my point is that it once you start
nesting you can no longer have the demuxer separate from the TAP
parser. So now it's tightly coupled with TAP which was supposedly a
bad thing.
We're talking at cross purposes. I'm proposing that begin/end be part
of TAP, handled by TAP parser.
I was also saying that if you want to multiplex multiple streams onto
a single pipe it should be implemented outside of TAP. That has
nothing to do with begin / end.
I added that to the example only for readability.
TAP's readability is a deliberate feature, any modifications should
retain that readability. You must have some kind of indentation.
We can certainly allow leading spaces. There's no need to /require/
correct indentation though.
Indenting by extending the number is somewhat backwards compatible.
And you're prepending a number to plan lines? To the TAP version
line? To each line of a YAML block?
How does the Test::More instance of each test script discover what
number it's supposed to prepend to each line? What happens if you
happen to want to merge two TAP transcripts that use the same prefix
number? Are we going to have to have a tool to renumber TAP?
Or we could just go with a proposal that adds two easily understood
keywords to TAP without altering any of the existing syntax.
--
Andy Armstrong, hexten.net
