Talk:TAP at IETF: Draft Standard/Closed

From Test Anything Protocol

These are closed discussions from the main discussion page. Please move them back there to continue them.

[edit] Whitespace

How strict do we want to be about whitespace? TAP::Parser::Grammar typically uses \s+ to match between elements. Do we want to put this lax view of whitespace into the RFC, or use a more strict single space to separate most tokens? Being strict will allow for simpler parsing, but it feels dishonest. --Schwern 03:31, 19 January 2009 (UTC)

AndyA sez go with sloppy whitespace. --Schwern

[edit] Newlines (closed)

How do we handle newlines? Right now it's system specific. This will become a problem as TAP is used as an archive format or streaming from one machine to another. Settling on one will interfere with reading raw TAP. For example, if we choose CRLF, the Internet newline, then Unix users will have trouble reading raw TAP output. OTOH the web seems to have no problem dealing with both newlines. --Schwern 03:33, 19 January 2009 (UTC)

It has been suggested to pick a single EOL and pretend there's a preprocessor which normalizes newlines. Apparently that's what XML does. --Schwern 00:58, 21 January 2009 (UTC)

I just incorporated that into the current description. -- Gaurav 12:01, 18 November 2009 (GMT)