comment on

I'm begining to think that for us Perl is actually more writeable/readable than XML,YAML,JSON,etc.

Agreed. Perl is the default choice. Although I find JSON (and to a lesser degree YAML) fairly easy to read, it's also easy to break when writing, and none of the parsers I tried gave feedback as useful as Perl's. My rule of thumb is that you should try to never use any tool that doesn't tell you which line number the problem is on.

However, I don't have the XML-phobia some people seem to have. It seems fine to me for config data. Verbose, but not that hard to deal with.

In reply to Re: Human readable/writable serialization alternatives to YAML and XML ? by perrin
in thread Human readable/writable serialization alternatives to YAML and XML ? by mandog

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.


Think about Loose Coupling
	PerlMonks