Re: Practical suggestion for accessing configuration data stored in XML format

I'm curious why you chose to roll your own config parser rather than use one of the existing Config::* modules.

This would certainly be my question if you were to consider submitting to CPAN.

Comment on Re: Practical suggestion for accessing configuration data stored in XML format

Replies are listed 'Best First'.
Re: Re: Practical suggestion for accessing configuration data stored in XML format by fuzzycow (Sexton) on Mar 18, 2003 at 15:45 UTC
I needed to represent tree-like configuration, and 1001 CPAN modules for parsing .ini files just didn't cut it I needed to describe module instance properties, and ties between instances (think: Application Server for perl module instances) I wanted to use method-based access to config options I wanted to use XML, so that in some distant feature I could use external 3rd party tools for config file generation I did not find anything that looked good in 'OO light' ;) Oh and btw, the module in its current state is the after-evolution of the module I wrote for the project	[reply]

Replies are listed 'Best First'.

Re: Re: Practical suggestion for accessing configuration data stored in XML format
by fuzzycow (Sexton) on Mar 18, 2003 at 15:45 UTC

I needed to represent tree-like configuration, and 1001 CPAN modules for parsing .ini files just didn't cut it

I needed to describe module instance properties, and ties between instances (think: Application Server for perl module instances)

I wanted to use method-based access to config options

I wanted to use XML, so that in some distant feature I could use external 3rd party tools for config file generation

I did not find anything that looked good in 'OO light' ;)

Oh and btw, the module in its current state is the after-evolution of the module I wrote for the project

[reply]