Best practice for configuration variables stored in external file

tunafish has asked for the wisdom of the Perl Monks concerning the following question:

So I was wondering what the best practice is for storing constants in an external file. I have scripts that I wrote before I heard of "use strict". The scripts share a configuration file, conf.pl, that defines things like database name, database user and password, paths to various folders, etc. Currently, the format is:

$constant_name = "constant_value";

I know this is wrong. What's the best way to do this?

Comment on Best practice for configuration variables stored in external file Download Code

Replies are listed 'Best First'.
Re: Best practice for configuration variables stored in external file by tobyink (Canon) on Sep 06, 2013 at 07:01 UTC
Config::Tiny is a reasonably good solution. `use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name`	[reply]
Re: Best practice for configuration variables stored in external file by McA (Priest) on Sep 06, 2013 at 07:20 UTC
Hi, I think your solution is not completely wrong. Put your constants into one or more perl modules an use (not import) them where you need it without polluting the namespace. Why shall a textfile which gets parsed by a module be better than a textfile (.pm) which gets parsed by perl itself? The question is: Do you need the ability to reconfigure at runtime (Constants are constant, aren't they)? Are the config constants bundled in a way, so that these constants belong to a component of your program. But this is the same problem as cutting your program into meaningful pieces (modules). Opinions from the illuminated monks appreciated. Best regards McA	[reply]
Re^2: Best practice for configuration variables stored in external file by afoken (Chancellor) on Sep 06, 2013 at 19:33 UTC
Constants belong into the code. Configuration options don't. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply]
Re^3: Best practice for configuration variables stored in external file by tunafish (Beadle) on Sep 08, 2013 at 01:51 UTC
I think then that I'm talking about "constants", not "configuration variables". They are not, at any point, edited from within the script. Would "use Module" then be the best way to handle this?	[reply]