config file q

quote from "notes/svn-config-files":

  Let's rethink this, and create a system which allows "nesty" syntax,
  something like scheme.

  The main point is still to define sections/keys/vals.

I'm not fully aware about for what the config files are gonna be used and for
what contents, but the wording of this remark made me think of some software
I wrote once. A config file system that is very hierarchical and I was
thinking something like that could be this 'which allows "nesty" syntax'.

It supports a config file that looks like:

foo{
  name{bar}
  version{2}
}
bar{
  name{foo}
  version{3}
  house{
   door{yes}
   window{no}
  }
}

... then an item can be fetched with their full names lile 'foo.name' or
'bar.house.door' and it allows traversing "directories" to get all the items
in the 'bar.house' directory etc.

In other words, if I knew some requirements I would consider taking on the
config file parsing.

-- 
      Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
   ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol