comment on

If you're going to use "do" you should pay more attention to the error variables it sets. Test $! and $@ (in that order) and provide an appropriate message that includes them so the user understands what they did wrong -- especially in the case of $@
If you're going to evaluate an arbitrary file, you should at least do some magic with Safe so that you don't have to worry about malicious people putting arbitrary code into an config file that was (mistakenly) left world writable.
Even if you don't use Safe, at the *least* you should but a nice big warning in the POD about the possibility of malicious code in config files

In reply to Re: RFC: Config::File by hossman
in thread RFC: Config::File by fireartist

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, details, 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, summary, 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.