I'd do it like this:
The INI
[GENERAL]
scheduledb=something
[SERVICE]
start2=stuff ${GENERAL/scheduledb=default} etcetera
The "getter":
sub x_val {
my ($ini,$sect,$key,$def)=@_; # same signature as 'val'
my $val=$ini->val($sect,$key,$def);
my ($sect1,$key1,$def1,$t);
while ($val=~/\$\{([^}]+)\}/) {
$t=$1;
($sect1,$key1,$def1)=($t=~m|^([^/]+)/([^=]+)(?:=(.*))?$|);
$val=$`.(x_val($ini,$sect1,$key1,$def1)).$';
}
$val;
}
Notes:
- It uses pre- and post-match variables, so it will slow you regexps
- The syntax is a bit different from the one you show
- It expands recursively
- It supports in-line defaults
- I haven't tested it...
--
dakkar - Mobilis in mobile
-
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.