- Use a data format that can be extended, like YAML.
Wow I never knew about that one - thats probably the solution. As I see it, the advantage of an XML solution is that the structure is well understood which means its easier for the logfile to be self documenting and thus is more maintainable in the event of my falling under a bus.
- If you insist on using XML, then parse it by pushing a fake root around of the file...
That was something I wanted to avoid. Its OK for a small logfile that can be hndled with XML::Simple, but if(when?) the log file grows then I'd like to migrate to XML::Twig or similar and then I can't do that.
Enter any 47-digit prime number to continue.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||