Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

config::file(3pm) [debian man page]

Config::File(3pm)					User Contributed Perl Documentation					 Config::File(3pm)

NAME
Config::File - Parse a simple configuration file SYNOPSIS
use Config::File; my $config_hash = Config::File::read_config_file($configuration_file); DESCRIPTION
"read_config_file" parses a simple configuration file and stores its values in an anonymous hash reference. The syntax of the configuration file is as follows: # This is a comment VALUE_ONE = foo VALUE_TWO = $VALUE_ONE/bar VALUE_THREE = The value contains a # (hash). # This is a comment. Options can be clustered when creating groups: CLUSTER_ONE[data] = data cluster one CLUSTER_ONE[value] = value cluster one CLUSTER_TWO[data] = data cluster two CLUSTER_TWO[value] = value cluster two Then values can be fetched using this syntax: $hash_config->{CLUSTER_ONE}{data}; There can be as many sub-options in a cluster as needed. BIG_CLUSTER[part1][part2][part3] = data is fetched by: $hash_config->{BIG_CLUSTER}{part1}{part2}{part3}; There are a couple of restrictions as for the names of the keys. First of all, all the characters should be alphabetic, numeric, underscores or hyphens, with square brackets allowed for the clustering. That is, the keys should conform to /^[A-Za-z0-9_-]+$/ This means also that no space is allowed in the key part of the line. CLUSTER_ONE[data] = data cluster one # Right CLUSTER_ONE[ data ] = data cluster one # Wrong Function ";read_config_file" Syntax Config::File::read_config_file($file); Arguments $file is the configuration file. Return value This function returns a hash reference. Each key of the hash is a value defined in the configuration file. Description "read_config_file" parses a configuration file a sets up some values in a hash reference. NOTES
Function not exported by default In versions up to 1.0, the function read_config_file was exported to the calling program's namespace - Starting in version 1.1, nothing is exported by default. You can either fully qualify read_config_file or explicitly import it into your namespace: Fully qualifying read_config_file use Config::File; my $config_hash = Config::File::read_config_file($configuration_file); Explicitly importing read_config_file use Config::File qw(read_config_file); my $config_hash = read_config_file($configuration_file); Migrated away from ConfigFile into Config::File As of version 1.4, in order to include this module in the CPAN, I decided to move away from the highly unstandard name of ConfigFile and rename the module to Config::File. A small redirecting module is put in place, so current code using this module does not break, but the ConfigFile namespace usage is deprecated (and will thus issue a warning). Please update your code! AUTHOR
Development was started by Sebastien J. Gross <seb@sjgross.org>, and since 2003 it is maintained by Gunnar Wolf <gwolf@gwolf.org>. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GPL. VERSION
Version 1.4 Copyright (c) 2002 Sebastien J. Gross. All rights reserved. Copyright (c) 2003-2009 Gunnar Wolf. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GPL v2 (or later, at your choice). perl v5.10.0 2009-02-20 Config::File(3pm)

Check Out this Related Man Page

INN::Config(3pm)					    InterNetNews Documentation						  INN::Config(3pm)

NAME
Config.pm - Export all the variables an INN Perl script might need DESCRIPTION
This Perl module sets up any and all the variables that an INN Perl script might need. More particularly, it allows to use inn.conf variables: they are all provided by innconfval, as well as the version of INN (in the variable $INN::Config::version). Other useful variables are also provided (directories, files, programs, masks, parameters) and you should have a look at the source code of the module to see what you can use in your Perl scripts. You only have to declare the module at the beginning of them: use lib '<pathnews>/lib/perl'; use INN::Config; Then, you can for instance use: print $INN::Config::localmaxartsize; to print the value of localmaxartsize as it is set in inn.conf. You can also specify a version when you import the module. If you write: use INN::Config 2.5.0; only versions of INN superior to 2.5.0 will be able to run the Perl script. It is also possible to import the variables directly in your namespace if you specify what you want to import: use INN::Config qw($localmaxartsize $pathbin); Note that a legacy innshellvars.pl is also provided in pathnews/lib for compatibility reasons with old Perl scripts not shipped with INN. It was used by versions of INN anterior to 2.5.0. The corresponding scripts for Shell and Tcl are, however, still in use: innshellvars and innshellvars.tcl. They offer the same capabilities as this module. HISTORY
innshellvars.pl was written by James Brister <brister@vix.com> for InterNetNews in 1996. It was converted to the INN::Config Perl module by Julien Elie in 2007. $Id: Config.pm.in 8357 2009-02-27 17:56:00Z iulius $ SEE ALSO
inn.conf(5), innconfval(1), perl(1). INN 2.5.2 2009-05-21 INN::Config(3pm)
Man Page