Re: YAML Was: CommitFest status/management

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

> Tallying up the votes on this patch

First, I would hope that you don't overlook the author of the patch (me)
as an "aye" vote. :) Additionally, if you are going to tally, please
consider the positive responses from people on -hackers and -general
when the patch was first posted and there was a question about what
the format would look like.

YAML is designed to be machine-parseable (just like XML) *AND*
human-readable (obstensibly like our current output). JSON tries
to overcome the shortcomings of XML, but doesn't quite get it right.
YAML does: it's small, intuitive, and only as verbose as needed. Human
readable, yet structured enough to be read by machines as well.

As far as the arguments for making an extensible system for supporting
other formats, but I think this is putting the cart before the horse.
While this feature is only in cvs at the moment, I've not heard a
single person state another format they would like to see. I cannot
think of one myself (machine parseable anyway: I'd love to see an
"abbreviated" version that takes out the explain bits of explain
analyze and changes rows= to R=, loops= to L=, etc.).

This is a small patch, easy to maintain, and useful to more people
than just myself, judging from the responses to the earlier thread.

ObPartingShot: I hope that those in the "machine readable output
should never be seen by human eyes" camp will support my upcoming
patch to remove all extra whitespace, including newlines, from the
XML format. :)

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation
PGP Key: 0x14964AC8 200912070727
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAksc9QMACgkQvJuQZxSWSshJXwCfeHrspp39mqGJD5Z86121F1Ap
VJEAoMIXrXe8/vS5rPnzyfbX04fJjp36
=H5BM
-----END PGP SIGNATURE-----