The following is an example of a valid config file - modified to include comments where the original of this (used in the test suite) does not.
// top level section
/*
* The original formulation of the concept only allowed sections at the top level
* After a bit of discussion, it was decided that this was a bit limiting.
*/
section {
# key to test operation and list parsing
key = [ list, op(! ident ), ident2 ]
# two keys, to test basic key-value pair testing and the important "all" key
# though "all" is kinda forgotten at this point and might go away
magic = xyzzy
all = ident3
// subsection to make sure that works
blech {
magic = abcd
}
}
Note that, as the comment in the example says, at one time the design called for there to be an "all" keyword for convenience. Handling that properly and making sure the various potential corner cases didn't happen is making me re-think its utility.