On 4/19/06, Ovid <[EMAIL PROTECTED]> wrote: > to handle got/expected failure information in Java or C? There are > pretty rich data structures we could put out there and YAML might help. > That would also likely simplify a parser.
If you mean you want pluck YAML test results from a noisy input stream Id say youd probably be wrong. YAML is about as inappropriate a tool for that purpose as I can imagine. Id say that using a white-space sensitive data representation in such a circumstance would be an abject nightmare. I should think that youd have a much easier time using Data::Dumper and its ->Pad and ->Indent(0) method than you ever would with YAML. DD output is more regular than YAML, and can be output so the full dump is on a single line meaning that buffering issues shouldnt be as difficult to resolve. Using ->Pad you could easily add a "magic marker" to identify the beginning of a dump stream (regardless as to its size). Heck with a DD structure you could use a regex to match the entire dump as DD's output is that predictable. Seriously Id be surprised to hear a single thing that makes YAML preferable to something like DD for the purposes I understand we are discussing. And i can think of a lot of reasons YAML would be suboptimal. cheers, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
