comment on

The only thing i prefer when munging HTML is meeting my clients' needs while working in the framework that they have. The ideals proposed by your module are noble indeed, but then the real world rears its ugly head and shatters those notions. Build it, and they will change it. My issues, however, are not with what Perl solutions to use, but rather how easy it is for someone post what the OP did and get away with it. Clever trolls be among us.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to Re^3: Why oh why is working with XML so bloomin' difficult in Perl? by jeffa
in thread Modified title: The structures created by many of the XML parsers in Perl appear unnecessarily deep in levels... by jfroebe

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.


Syntactic Confectionery Delight
	PerlMonks