it is rather annoying to run into the limits of your tool before you run into the limits of your project.
Yes it is. I'm currently in the planing phase on how to rewrite my big projects XML config parser. Which, incidently, is XML::Simple based. While it works quite nicely, it takes some, uh, not-so-nice workaround thinking when writing the config files itself. I must admit, when i started this project, it was the first time i used XML for configuration files. And it was Plug-and-Play, really and saved me quite some time to get started.
Still, i'll probably keep XML::Simple around for all those small convert-this-into-that tools. For the typical ten-settings-and-five-comments config files for these kind of tools it is just ideal.
So, XML::Simple is a two sided sword. It highly depends on your requirements.
BREW /very/strong/coffee HTTP/1.1
418 I'm a teapot
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||