in reply to Parsing a complex config file

I don't have time to code a solution write now, but I have time to comment on the structure you wish the parser to output.

The following structure contains all the information as yours, but is more concise. Simpler is almost always better.

@domains = ( { 'libname' => 'foo', ... 'options|roptions' => { 'datapath' => [ ... ], 'indexpath' => [ ... ], 'workpath' => [ ... ], 'metapath' => [ ... ], }, }, { 'libname' => 'bar', ... 'options|roptions' => { 'datapath' => [ ... ], 'indexpath' => [ ... ], 'workpath' => [ ... ], 'metapath' => [ ... ], }, }, );

Replies are listed 'Best First'.
Re^2: Parsing a complex config file
by Anonymous Monk on Jul 12, 2006 at 13:29 UTC
    I agree, simpler is better...
    • no point now that I think about it...I agree.
    • that would be due to me being rusty...this makes sense.


    I'll be adjusting my structure to reflect this.

    thanks