With YAML you can do this:
use YAML;
my $href = ""> foo => 'bar'
baz => 'quoxx'
$fnord => [EMAIL PROTECTED]
}
print Dump $href;
and get a YAML dump of what the config datastructure is supposed to look like without problem. This is too useful to discard. From my cursory reading of the docs, Config::General doesn't seem to support this. JSON probably does, but then looks rather code like to me. As for XML by default, well - no thanks, please no.
On 10/06/06, Matt S Trout <[EMAIL PROTECTED]> wrote:
I love YAML as a serialisation format for data transfer, but so far as stuff
like config files that are designed for human write / machine read, I
personally think it sucks. Massively.
And for hysterical raisins it's currently our default config file formats, and
I see users running into trouble getting their myapp.yml to parse right all
the flipping time. So, I'm wondering if this is just me being a YAML-hating
heretic or if other people are of the same opinion.
A few (IMO) better options -
Config::General -
<View TT>
INCLUDE_PATH __path_to('root')__
</View>
JSON -
{
'View::TT': {
INCLUDE_PATH: "__path_to('root')__"
}
}
INI-style -
[View::TT]
INCLUDE_PATH=__path_to('root')__
What do you all think, then? (/me dons asbestos suit, waits for the holy war
to start :)
--
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information
+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +
_______________________________________________
Catalyst mailing list
[EMAIL PROTECTED]
http://lists.rawmode.org/mailman/listinfo/catalyst
_______________________________________________ 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/
