If you know the location of the config file relative to the script which uses your module, you can use
FindBin:
# Parent script resides in /usr/local/myproject/bin
# Module and config file reside in /usr/local/myproject/lib
use FindBin qw($Bin);
sub get_config
{
my $CONFIGPATH = "$Bin/../lib/acme.config";
open (CONFIG, "<$CONFIGPATH") or die "$0: File '$CONFIGPATH': $!";
undef $/;
my $c=<CONFIG>;
close CONFIG;
return $c;
}
A couple of other notes:
<list>
You should get in the habit of explicitly directing your open() calls. E.g. use "<$CONFIGFILE" instead of "$CONFIGFILE". In this particular case it isn't a big deal, but if $CONFIGFILE was supplied by a user, that user could set it to something bad like "|rm -rf /*".
chomp() operates directly on the variable you give it as an argument, so returning chomp($c) won't do what you think it does.
chomp() doesn't do anything at all in slurp mode ($/ = undef) anyway. :)
</list>
-Matt
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.