Re: [tap] RFC Status?

[Steffen Schwigon <[e-mail]>]

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 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.


> As for the YAMLish structured diagnostics, those were never official,
> [...]
> whether or not we should use YAML or JSON
> [...]
> If you asked me what my stance is today, I would think that
> structured diagnostics should valid JSON

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.

Kind regards,
Steffen,
 (probably the most hardcore TAP user on earth)
-- 
Steffen Schwigon <[e-mail]>