All the Perl that's Practical to Extract and Report
use Perl Log In
Ovid (2709)
Ovid
(email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)
(email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)
Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.
Saturday April 05, 2008
05:47 AM
Oslo: TAP Diagnostics
Sitting in Oslo right now. We are now nailing down the new YAML diagnostic syntax. Tentatively we have something like this:
TAP version 14
1..4
ok 1 - Input file opened
not ok 2 - First line of the input valid
---
results:
have: 'Flirble'
want: 'Fnible'
severity: fail
file: t/foo.t
line: 12
tags:
- IO
- config
source: is $line[0], 'Fnible', 'First line of the input valid';
...
There are other keys like 'timestamp', url', 'display' and similar that will likely be included. All are optional.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
--Larry Wall in eval.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
YAML (Score:1)
Please make sure to specify that the diagnostics have to conform to the YAML Tiny [cpan.org] subset of YAML.
Re: (Score:2)
Why? Do recall that this is also be allowed for other languages with different data structures with different serialization requirements.
Re: (Score:1)
Precisely. YAML is not suitable for high-fidelity serialisation. You really want eg. Data::Dump::Streamer if your data structures are tricky.
However, writing a YAML parser is a much bigger job than writing a TAP parser. Parsing YAML Tiny is on par with parsing TAP, and the dialect is perfectly sufficient for modest serialisation needs.
So demanding a full YAML parser to parse TAP won’t provide substantial benefit but may hamper adoption of TAP.