So the big problem with aXML is the non-aXML compliant code you want to run through it?
That's like trying to say that Perl is broken because it doesn't natively run COBOL.
The (inc) command can load your file fine... then you just wrap it with a plugin of your design to get the output. In a similar way to how you would layer middleware components.
How about you show me a fragment of the file, and tell me what output would be required from processing it, please make the task as extra-specially difficult as you possibly can, fiendishly difficult even, the harder the better. I'm pretty confident I can still show you an elegant solution.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.