On 7/10/06, Ian Langworth <[EMAIL PROTECTED]> wrote:
These diagnostic keywords seem to blend too much into the rest of TAP.
Look at it in a fixed-with font, if you're not already, and it might stand out better. Also consider that with the next gen TAP parsers, "enhanced" TAP displays should be easier. ie. Reading the raw TAP but with color, emphesis, etc...
Consider: not ok 2 - omg t3h sooper test!!1! ! file: foo.t ! line: 45 ! description: omg t3h sooper test!!1! ! got: this ! expected: that ! raw-test: is( "this", "that", "omg t3h sooper test!!1!" ); ! x-THAC0: 16 ...or some other delimiter.
I do like this idea because it makes it clearer what is and what is not a diagnostic line, for parsing purposes, rather than "whatever happens to parse as YAML".
Or maybe we say that any inline YAML is interpreted as a comment data structure
*head scratch* But if it has parsable structure its not a comment...
instead of a giant comment string, which can be used for diagnostics: not ok 2 - omg t3h sooper test!!1! --- TAP diagnostics file: foo.t line: 45 description: omg t3h sooper test!!1! got: this expected: that raw-test: is( "this", "that", "omg t3h sooper test!!1!" ); x-THAC0: 16
The "-- TAP" doesn't do much for me visually. I guess I see where you're going, making the YAML bits explicit for the parser, but where do we stop parsing?
