<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Grammar</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>
<body style="background-color: white">
<p><a name="__index__"></a></p>
<!-- INDEX BEGIN -->
<!--
<ul>
<li><a href="#name">NAME</a></li>
<li><a href="#synopsis">SYNOPSIS</a></li>
<li><a href="#description">DESCRIPTION</a></li>
<ul>
<li><a href="#grammar_definition">Grammar Definition</a></li>
<ul>
<li><a href="#special_section_keys">Special Section Keys</a></li>
<li><a href="#special_variable_keys">Special Variable Keys</a></li>
<li><a href="#special_table_keys">Special Table Keys</a></li>
<li><a href="#special_text_keys">Special Text Keys</a></li>
</ul>
<li><a href="#configuration_syntax">Configuration Syntax</a></li>
<ul>
<li><a href="#general_syntax">General Syntax</a></li>
<li><a href="#sections">Sections</a></li>
<li><a href="#assignments">Assignments</a></li>
<li><a href="#tabular_data">Tabular Data</a></li>
</ul>
<li><a href="#example">Example</a></li>
<ul>
<li><a href="#code">Code</a></li>
<li><a href="#configuration">Configuration</a></li>
<li><a href="#result">Result</a></li>
</ul>
</ul>
<li><a href="#see_also">SEE ALSO</a></li>
<li><a href="#copyright">COPYRIGHT</a></li>
<li><a href="#license">LICENSE</a></li>
<li><a href="#authors">AUTHORS</a></li>
</ul>
-->
<!-- INDEX END -->
<p>
</p>
<h1><a name="name">NAME</a></h1>
<p>Config::Grammar - A grammar-based, user-friendly config parser</p>
<p>
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
<pre>
use Config::Grammar;</pre>
<pre>
my $parser = Config::Grammar->new(\%grammar);
my $cfg = $parser->parse('app.cfg') or die "ERROR: $parser->{err}\n";
my $pod = $parser->makepod();
my $ex = $parser->maketmpl('TOP','SubNode');
my $minex = $parser->maketmplmin('TOP','SubNode');</pre>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
<p>Config::Grammar is a module to parse configuration files. The
configuration may consist of multiple-level sections with assignments
and tabular data. The parsed data will be returned as a hash
containing the whole configuration. Config::Grammar uses a grammar
that is supplied upon creation of a Config::Grammar object to parse
the configuration file and return helpful error messages in case of
syntax errors. Using the <strong>makepod</strong> method you can generate
documentation of the configuration file format.</p>
<p>The <strong>maketmpl</strong> method can generate a template configuration file. If
your grammar contains regexp matches, the template will not be all
that helpful as Config::Grammar is not smart enough to give you sensible
template data based in regular expressions. The related function
<strong>maketmplmin</strong> generates a minimal configuration template without
examples, regexps or comments and thus allows an experienced user to
fill in the configuration data more efficiently.</p>
<p>
</p>
<h2><a name="grammar_definition">Grammar Definition</a></h2>
<p>The grammar is a multiple-level hash of hashes, which follows the structure of
the configuration. Each section or variable is represented by a hash with the
same structure. Each hash contains special keys starting with an underscore
such as '_sections', '_vars', '_sub' or '_re' to denote meta data with information
about that section or variable. Other keys are used to structure the hash
according to the same nesting structure of the configuration itself. The
starting hash given as parameter to 'new' contains the ``root section''.</p>
<p>
</p>
<h3><a name="special_section_keys">Special Section Keys</a></h3>
<dl>
<dt><strong><a name="item__sections">_sections</a></strong>
</dt><dd>
<p>Array containing the list of sub-sections of this section. Each sub-section
must then be represented by a sub-hash in this hash with the same name of the
sub-section.</p>
<p>The sub-section can also be a regular expression denoted by the syntax '/re/',
where re is the regular-expression. In case a regular expression is used, a
sub-hash named with the same '/re/' must be included in this hash.</p>
</dd><dt><strong><a name="item__vars">_vars</a></strong>
</dt><dd>
<p>Array containing the list of variables (assignments) in this section.
Analogous to sections, regular expressions can be used.</p>
</dd><dt><strong><a name="item__mandatory">_mandatory</a></strong>
</dt><dd>
<p>Array containing the list of mandatory sections and variables.</p>
</dd><dt><strong><a name="item__inherited">_inherited</a></strong>
</dt><dd>
<p>Array containing the list of the variables that should be assigned the
same value as in the parent section if nothing is specified here.</p>
</dd><dt><strong><a name="item__table">_table</a></strong>
</dt><dd>
<p>Hash containing the table grammar (see Special Table Keys). If not specified,
no table is allowed in this section. The grammar of the columns if specified
by sub-hashes named with the column number.</p>
</dd><dt><strong><a name="item__text">_text</a></strong>
</dt><dd>
<p>Section contains free-form text. Only sections and @includes statements will
be interpreted, the rest will be added in the returned hash under '_text' as
string.</p>
<p><strong>_text</strong> is a hash reference which can contain a <strong>_re</strong> and a <strong>_re_error</strong> key
which will be used to scrutanize the text ... if the hash is empty, all text
will be accepted.</p>
</dd><dt><strong><a name="item__order">_order</a></strong>
</dt><dd>
<p>If defined, a '_order' element will be put in every hash containing the
sections with a number that determines the order in which the sections were
defined.</p>
</dd><dt><strong><a name="item__doc">_doc</a></strong>
</dt><dd>
<p>Describes what this section is about</p>
</dd><dt><strong><a name="item__sub">_sub</a></strong>
</dt><dd>
<p>A function pointer. It is called for every instance of this section,
with the real name of the section passed as its first argument. This is
probably only useful for the regexp sections. If the function returns
a defined value it is assumed that the test was not successful and an
error is generated with the returned string as content.</p>
</dd></dl>
<p>
</p>
<h3><a name="special_variable_keys">Special Variable Keys</a></h3>
<dl>
<dt><strong><a name="item__re">_re</a></strong>
</dt><dd>
<p>Regular expression upon which the value will be checked.</p>
</dd><dt><strong><a name="item__re_error">_re_error</a></strong>
</dt><dd>
<p>String containing the returned error in case the regular expression doesn't
match (if not specified, a generic 'syntax error' message will be returned).</p>
</dd><dt><strong>_sub</strong>
</dt><dd>
<p>A function pointer. It called for every value, with the value passed as its
first argument. If the function returns a defined value it is assumed that
the test was not successful and an error is generated with the returned
string as content.</p>
<p>If the '_varlist' key (see above) is defined in this section, the '_sub'
function will also receive an array reference as the second argument. The
array contains a list of those variables already defined in the same
section. This can be used to enforce the order of the variables.</p>
</dd><dt><strong><a name="item__default">_default</a></strong>
</dt><dd>
<p>A default value that will be assigned to the variable if none is specified or inherited.</p>
</dd><dt><strong>_doc</strong>
</dt><dd>
<p>Description of the variable.</p>
</dd><dt><strong><a name="item__example">_example</a></strong>
</dt><dd>
<p>A one line example for the content of this variable.</p>
</dd></dl>
<p>
</p>
<h3><a name="special_table_keys">Special Table Keys</a></h3>
<dl>
<dt><strong><a name="item__columns">_columns</a></strong>
</dt><dd>
<p>Number of columns. If not specified, it will not be enforced.</p>
</dd><dt><strong><a name="item__key">_key</a></strong>
</dt><dd>
<p>If defined, the specified column number will be used as key in a hash in the
returned hash. If not defined, the returned hash will contain a '_table'
element with the contents of the table as array. The rows of the tables are
stored as arrays.</p>
</dd><dt><strong>_sub</strong>
</dt><dd>
<p>they work analog to the description in the previous section.</p>
</dd><dt><strong>_doc</strong>
</dt><dd>
<p>describes the content of the column.</p>
</dd><dt><strong>_example</strong>
</dt><dd>
<p>example for the content of this column</p>
</dd></dl>
<p>
</p>
<h3><a name="special_text_keys">Special Text Keys</a></h3>
<dl>
<dt><strong>_re</strong>
</dt><dd>
<p>Regular expression upon which the text will be checked (everything as a single
line).</p>
</dd><dt><strong>_re_error</strong>
</dt><dd>
<p>String containing the returned error in case the regular expression doesn't
match (if not specified, a generic 'syntax error' message will be returned).</p>
</dd><dt><strong>_sub</strong>
</dt><dd>
<p>they work analog to the description in the previous section.</p>
</dd><dt><strong>_doc</strong>
</dt><dd>
<p>Ditto.</p>
</dd><dt><strong>_example</strong>
</dt><dd>
<p>Potential multi line example for the content of this text section</p>
</dd></dl>
<p>
</p>
<h2><a name="configuration_syntax">Configuration Syntax</a></h2>
<p>
</p>
<h3><a name="general_syntax">General Syntax</a></h3>
<p>'#' denotes a comment up to the end-of-line, empty lines are allowed and space
at the beginning and end of lines is trimmed.</p>
<p>'\' at the end of the line marks a continued line on the next line. A single
space will be inserted between the concatenated lines.</p>
<p>'@include filename' is used to include another file. Include works relative to the
directory where the parent file is in.</p>
<p>'@define a some value' will replace all occurences of 'a' in the following text
with 'some value'.</p>
<p>Fields in tables that contain white space can be enclosed in either <code>'</code> or <code>"</code>.
Whitespace can also be escaped with <code>\</code>. Quotes inside quotes are allowed but must
be escaped with a backslash as well.</p>
<p>
</p>
<h3><a name="sections">Sections</a></h3>
<p>Config::Grammar supports hierarchical configurations through sections, whose
syntax is as follows:</p>
<dl>
<dt><strong><a name="item_level_1">Level 1</a></strong>
</dt><dd>
<p>*** section name ***</p>
</dd><dt><strong><a name="item_level_2">Level 2</a></strong>
</dt><dd>
<p>+ section name</p>
</dd><dt><strong><a name="item_level_3">Level 3</a></strong>
</dt><dd>
<p>++ section name</p>
</dd><dt><strong><a name="item_level_n_2c_n_3e1">Level n, n>1</a></strong>
</dt><dd>
<p>+..+ section name (number of '+' determines level)</p>
</dd></dl>
<p>
</p>
<h3><a name="assignments">Assignments</a></h3>
<p>Assignements take the form: 'variable = value', where value can be any string
(can contain whitespaces and special characters). The spaces before and after
the equal sign are optional.</p>
<p>
</p>
<h3><a name="tabular_data">Tabular Data</a></h3>
<p>The data is interpreted as one or more columns separated by spaces.</p>
<p>
</p>
<h2><a name="example">Example</a></h2>
<p>
</p>
<h3><a name="code">Code</a></h3>
<pre>
use Data::Dumper;
use Config::Grammar;</pre>
<pre>
my $RE_IP = '\d+\.\d+\.\d+\.\d+';
my $RE_MAC = '[0-9a-f]{2}(?::[0-9a-f]{2}){5}';
my $RE_HOST = '\S+';</pre>
<pre>
my $parser = Config::Grammar->new({
_sections => [ 'network', 'hosts' ],
network => {
_vars => [ 'dns' ],
_sections => [ "/$RE_IP/" ],
dns => {
_doc => "address of the dns server",
_example => "ns1.oetiker.xs",
_re => $RE_HOST,
_re_error =>
'dns must be an host name or ip address',
},
"/$RE_IP/" => {
_doc => "Ip Adress",
_example => '10.2.3.2',
_vars => [ 'netmask', 'gateway' ],
netmask => {
_doc => "Netmask",
_example => "255.255.255.0",
_re => $RE_IP,
_re_error =>
'netmask must be a dotted ip address'
},
gateway => {
_doc => "Default Gateway address in IP notation",
_example => "10.22.12.1",
_re => $RE_IP,
_re_error =>
'gateway must be a dotted ip address' },
},
},
hosts => {
_doc => "Details about the hosts",
_table => {
_doc => "Description of all the Hosts",
_key => 0,
_columns => 3,
0 => {
_doc => "Ethernet Address",
_example => "0:3:3:d:a:3:dd:a:cd",
_re => $RE_MAC,
_re_error =>
'first column must be an ethernet mac address',
},
1 => {
_doc => "IP Address",
_example => "10.11.23.1",
_re => $RE_IP,
_re_error =>
'second column must be a dotted ip address',
},
2 => {
_doc => "Host Name",
_example => "tardis",
},
},
},
});</pre>
<pre>
my $cfg = $parser->parse('test.cfg') or
die "ERROR: $parser->{err}\n";
print Dumper($cfg);
print $parser->makepod;</pre>
<p>
</p>
<h3><a name="configuration">Configuration</a></h3>
<pre>
*** network ***
dns = 192.168.7.87
+ 192.168.7.64
netmask = 255.255.255.192
gateway = 192.168.7.65
*** hosts ***
00:50:fe:bc:65:11 192.168.7.97 plain.hades
00:50:fe:bc:65:12 192.168.7.98 isg.ee.hades
00:50:fe:bc:65:14 192.168.7.99 isg.ee.hades</pre>
<p>
</p>
<h3><a name="result">Result</a></h3>
<pre>
{
'hosts' => {
'00:50:fe:bc:65:11' => [
'00:50:fe:bc:65:11',
'192.168.7.97',
'plain.hades'
],
'00:50:fe:bc:65:12' => [
'00:50:fe:bc:65:12',
'192.168.7.98',
'isg.ee.hades'
],
'00:50:fe:bc:65:14' => [
'00:50:fe:bc:65:14',
'192.168.7.99',
'isg.ee.hades'
]
},
'network' => {
'192.168.7.64' => {
'netmask' => '255.255.255.192',
'gateway' => '192.168.7.65'
},
'dns' => '192.168.7.87'
}
};</pre>
<p>
</p>
<hr />
<h1><a name="see_also">SEE ALSO</a></h1>
<p><a href="./Config/Grammar/Dynamic.html">the Config::Grammar::Dynamic manpage</a></p>
<p>
</p>
<hr />
<h1><a name="copyright">COPYRIGHT</a></h1>
<p>Copyright (c) 2000-2005 by ETH Zurich. All rights reserved.
Copyright (c) 2007 by David Schweikert. All rights reserved.</p>
<p>
</p>
<hr />
<h1><a name="license">LICENSE</a></h1>
<p>This program is free software; you can redistribute it and/or modify it
under the same terms as Perl itself.</p>
<p>
</p>
<hr />
<h1><a name="authors">AUTHORS</a></h1>
<p>David Schweikert,
Tobias Oetiker,
Niko Tyni</p>
</body>
</html>
distrib
>
Mandriva
>
2010.0
>
i586
>
media
>
contrib-release
>
by-pkgid
>
d97b4c58d8763adc61a7b020afdfd868
>
files
>
21
