Re: [tap] RFC Status?

[Leon Timmermans <[e-mail]>]

On Fri, Sep 19, 2014 at 5:59 PM, Steffen Schwigon <[e-mail]>
wrote:

> Ovid <[e-mail]> writes:
> > For subtests, they are indented four spaces. Always four spaces.
>
> Bummer! This was an eye-opener for me, in a sense that IMHO with this
> nested TAP we step into a nested hell of context sensitive whitespace
> parsing, which, as additional bonus, isn't human-readable anymore, and,
> as additional additional bonus, already evidently seems to be hard to
> implement.
>

I'd agree the lack of a clear opener is unfortunate. Parsing it requires
one to maintain more state than desirable.


> I might exaggerate here slightly, but seriously, is it really worth?
>
> Which use-case can't live with today's TAP when structuring its tests in
> separate test files, respective TAP streams.
>

I can see the use for it, but it certainly adds complications.

And here I seriously start to panic if that opinion should ever lead to
> deprecating YAMLish, as 1) it much better fits the philosophy of TAP's
> line-based'ness, 2) is easier to generate with line based tools, like in
> a shell-only world, and 3) zillions of test results are already based on
> it for the last 6 years. I'm not exaggerating here.


I wasn't aware of anyone actually outputting YAML. Can you tell us more
about this?

Leon