Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
These snippets illustrate the following:
Configuration data is aggregated in hashes (just one for these snippets) to cut down on the number of variable names.
The configuration hashes are maintained in their own namespace to avoid collisions.
Configuration files are maintained in Perl syntax for easy reading, writing and syntax verification.
By maintaining config data in a hash, you can not only quickly access key-value pairs, but also maintain more complex data. For example,
%CFG = ( 'servers' => { 'SRV1' => { 'IP' => 99.32.4.0, 'user' => 'aname', 'pswd' => 'p4ssw0rd', 'status' => 'unavailable' }, 'SRV2' => { 'IP' => 129.99.10.5 'user' => 'guest', 'pswd' => 'guest' 'status' => 'unavailable' } }, 'timeout' => 60, 'log' => { 'file' => '/var/log/my_log.log', 'level' => 'warn', }, 'temp' => 'remove me' );
Maintaining config data in Perl syntax makes it easy to read:
# Read a configuration file # The arg can be a relative or full path, or # it can be a file located somewhere in @INC. sub ReadCfg { my $file = $_[0]; our $err; { # Put config data into a separate namespace package CFG; # Process the contents of the config file my $rc = do($file); # Check for errors if ($@) { $::err = "ERROR: Failure compiling '$file' - $@"; } elsif (! defined($rc)) { $::err = "ERROR: Failure reading '$file' - $!"; } elsif (! $rc) { $::err = "ERROR: Failure processing '$file'"; } } return ($err); } # Get our configuration information if (my $err = ReadCfg('my_cfg.cfg')) { print(STDERR $err, "\n"); exit(1); }
The config data is easy to access in its own namespace:
# Add last access time $CFG::CFG{'servers'}{'SRV1'}{'last_access'} = time(); # Change server availablility $CFG::CFG{'servers'}{'SRV1'}{'status'} = 'online'; # Delete temporary data delete($CFG::CFG{'temp'}); # Open log file my $LOG; if (! open($LOG, "> $CFG::CFG{'log'}{'file'}")) { print(STDERR "ERROR: Failure opening log file: $!\n"); exit(1); }
The Data::Dumper module lets you write config data easily:
use Data::Dumper; # Save configuration data # Use the same arg as used with ReadCfg() # so that file can be found in the %INC. sub SaveCfg { my $file = $INC{$_[0]}; my $CFG; if (! open($CFG, "> $file")) { return ("ERROR: Failure opening '$file' - $!"); } print $CFG <<_MARKER_; ##### # # My configuration file # ##### use strict; use warnings; our (%CFG); # The configuration data @{[Data::Dumper->Dump([\%CFG::CFG], ['*CFG'])]} 1; # EOF _MARKER_ close($CFG); return (undef); # Success } # Save our configuration file if (my $err = SaveCfg('my_cfg.cfg')) { print(STDERR $err, "\n"); exit(1); }
The syntax of the config file can be easily checked using:
perl -c my_cfg.cfg

In reply to Reading and Writing Perl Config Files by jdhedden

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others about the Monastery: (6)
As of 2024-03-29 00:37 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found