* Joel Bernstein <[EMAIL PROTECTED]> [2007-01-29 18:30]: > I think the difficulty here is that Config::Any::_load has the > potential if running without use_ext=>1 to generate a lot of > spurious warnings caused by all the plugins to which a given > config file is offered, but which can't parse the file. So any > patch would presumably only report warnings if use_ext=>1. But > that still doesn't seem ideal. Suggestions?
Just warn if the file fails with *all* parsers. We’ve got a config file; we can reasonably assume that one of the parsers will be able to make sense of it. If none of them can, since it’s still a config file, it’s obviously a broken one. 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/
