On Fri, Jun 09, 2006 at 04:04:09PM +0100, Andrew Ford wrote: > I totally agree with this. YAML is fine as a serialization format, and > it can be useful that it is (just about) readable, but I find it insane > that it is even considered usable as a configuration file format -- it > is just too easy to break and reinforces the prejudice that perl is just > for hackers. For applications that may need their configurations > tweaking by client's support staff I have generally used Windows-style > .ini files (parsed with Config::IniFiles). I know the format is limited > to groups of keyword/value pairs, but that generally suffices and keeps > things so that they are simple to explain.
I put client config options in the database, and application level config in YAML or sometimes just a perl hash read by do(). If they can't figure out YAML then they probably shouldn't be in there tweaking the config in the first place. ;) -- Bill Moseley [EMAIL PROTECTED] _______________________________________________ Catalyst mailing list [EMAIL PROTECTED] http://lists.rawmode.org/mailman/listinfo/catalyst
