- 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.
Dingus Enter any 47-digit prime number to continue.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|