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

Why not post the module source here as an RFC?

If it is prohibitively big, extract the code chunks that are important and where the design choices were made.

My comments on the approach--If I chose to use XML for a config file, I would probably use XPath and XSL Templates to get out the info I need. Using XML, without using XPath or XSLT, is just doing it the hard way, IMHO.

--Solo

--
No. I don't think the Empire had Wookiees in mind when they designed her, Chewie.

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 17:29 UTC
I can not post the code at the moment because of the possible intellectual property issues with my employer. I wanted to see if somebody needs something like this, before I start sorting out the issue with my bosses. The amount of work needed to make the module release worthy is also an issue ;)	[reply]
Re^3: Practical suggestion for accessing configuration data stored in XML format by mojotoad (Monsignor) on Mar 18, 2003 at 19:06 UTC
The amount of work needed to make the module release worthy is also an issue ;) Just an observation here -- I've found that when working on a module of any significance in the workplace, it pays off to write the module as if you were going to release it to CPAN -- even if you never plan on doing so. By coding with this assumption in mind I am far less likely to cut corners, because there's always a chance that my dirty underwear will be strung out on the line. And really, whoever ends up maintaining your code will thank you for the extra attention to detail. Matt	[reply]
Re: Re^3: Practical suggestion for accessing configuration data stored in XML format by Anonymous Monk on Mar 19, 2003 at 09:16 UTC
It is my firm belief that every single piece of code you write should be of such a quality that you'd be proud to post it in popular public fora. It has always been my experience that any code I don't take this care in writing comes back to haunt me many times over. Document everything, carefully consider your apis, and keep it as simple as possible. You'll thank yourself down the road.	[reply]