I use a default location (using FindBin if the default location is the code directory) and a command line argument to change it if needed: 

use YAML qw(LoadFile);          # my config files are often in YAML
use FindBin qw($Bin);           # $Bin gives the code directory
use Getopt::Std;                # Getopt::Long is probably better

my %opt;
getopts( 'c:' => \%opt);        # -c <config_file>

$opt{c} ||= "$Bin/config.yaml"; # default location

# this is far from perfect, I should really open the file properly,
# slurp it and then use YAML to parse the content
# as it is, if the file exists but cannot be opened the
# error message is a bit ugly... 
die "cannot find file config file $opt{c}" unless( -f $opt{c});

my $env= LoadFile( $opt{c});

[download]

In reply to Re: Avoiding hard-coding by mirod
in thread Avoiding hard-coding by Sprad

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.