I'd do it like this:

The INI

[GENERAL]
scheduledb=something
[SERVICE]
start2=stuff ${GENERAL/scheduledb=default} etcetera
[download]

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;
}
[download]

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

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.