also sprach Joey Hess <jo...@debian.org> [2014-09-09 21:10 +0200]:
> You make it sound like it's walking the filesystem tree, but it's not,
> it's messing around in its data structures from the configs it's already
> loaded.

It's actually using dirname($dir) in a while loop, but it uses the
dirname to index into the $config structure. So: both. ;)

> I have not touched this code since it was written, but I belive
> this is how DEFAULT stanzas get inherited around to be available
> by other stanzas.

The question seems to be: if every loadconfig() run only merges the
first parent's $config{'DEFAULT'} into the current DEFAULT, then
is this first parent's DEFAULT guaranteed to contain its parent's
DEFAULT at the time of the merge? I cannot really gather this from
the code, maybe because I am looking at it with a different lense
(cf. my interpretation of backtracking without the need for chaining
in #743576).

-- 
 .''`.   martin f. krafft <madduck@d.o> @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
"it is the mark of an educated mind
 to be able to entertain a thought
 without accepting it."
                                                        -- aristoteles

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Reply via email to