Re: RFC - kernel test result specification (KTAP)

-----Original Message-----
From: Kees Cook <redacted>

On Mon, Aug 30, 2021 at 05:48:07PM +0000, Tim.Bird@sony.com wrote:

quoted

From: Kees Cook <redacted>

...

quoted

quoted

Yes, though the optional "- " is strictly part of the optional
description.

It's mildly annoying that "-" is optional.  It's trivial to deal with in the parser
to just ignore it if it's present.  But it has no semantic meaning whatsoever.
IMHO it would be nice to either mandate it or remove it, for consistency's sake.
This could be based solely on the consensus for whether it added or detracted
from human readability, since parsers don't care.

I have no strong opinion on the "-". I was surprised to encounter it
as it's not part of the TAP 13 spec. I would prefer to drop it, if I had
to choose.

The TAP 13 specification does not mention "-", but a dash on the result line
is used in most of the examples shown in the specification here:
http://testanything.org/tap-specification.html

In the top two examples on that page, the first one does not use dashes and
the second one does.  It's kind of irritating to have that kind of loosey-goosey
syntax in a specification.  IMHO the syntax should be more strictly specified
than this.  I don't have a strong opinion either on whether to use dashes or not.
But it would be nice to make it consistent.
 -- Tim Bird