* Matt S Trout <[EMAIL PROTECTED]> [2006-06-09 17:35]: > A few (IMO) better options - > > Config::General - > JSON - > INI-style -
INI is just too limited for use as the default format. JSON has the problem that non-programmers don’t know about lists and hashes and all that, so to them the necessary placement of parens and braces appears magical. YAML has the same problem, only much worse, because the syntax relies on whitespace, dashes and colons. Their placement seems even more confounding even if it is conceptually equivalent to JSON. Apache-style is basically like INI, except that it has provisions for nested sections. (Directives don’t look exactly like INI, but the differences are only superficial.) The taggish way of denoting sections is a bit verbose, but is actually easier for non-programmers to figure out than something brace-based, and also makes large documents easier to visually parse than dainty punctuation. The only downer is that Config::General can’t serialise a config to something quite as pretty-looking as a human can write it, but that’s entirely livable. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> _______________________________________________ List: [EMAIL PROTECTED] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ Dev site: http://dev.catalyst.perl.org/
