I quite often provide Perl apps compiled into executables with perl2exe for deployment on systems without Perl installed. As such I always provide a back-door means by which the configuration can be adjusted e.g.: -
use strict;
my $cake = 'chocolate';
my $pie = 'apple';
eval slurp("config.pl");
Which will run config.pl at run time assuming a nice handy slurp function is provided to read a file...
## slurp - read a file into a scalar or list
sub slurp {
my $file = shift;
local *F;
open F, "< $file" or die "Error opening '$file' for read: $!";
if(not wantarray){
local $/ = undef;
my $string = <F>;
close F;
return $string;
}
local $/ = "";
my @a = <F>;
close F;
return @a;
}
So when config.pl contains...
$pie = 'pecan';
cake = 'fairy';
...the pie and cake get set to your favourites rather than the defaults.
If you are interested in errors from the eval, it can be followed by something like...
if($@){
print "Some errors happened...\n\n";
print $@."\n\n";
print "Oh well...\n";
}
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.