there is no guarantee that the output remains wellformed when tickers are patched or newly created

F.U.D. Demonstrate how that's likely to break.

XML::Fling was designed to take the important (likely to break) aspects of well-formed XML into account. Sure, you can do really stupid things with it that would produce obviously broken XML because it doesn't waste time checking for obviously stupid things, but I don't see a problem there.

And you can stop suggesting alternate ways of handling control characters. I've been through a bunch but when XML 1.1 showed signs of sanity, the two choices of "strip 'em" and "leave 'em be" became the hands-down winners.

So you are restricted to the ways of using Genx that I've already stated: As an optional alternative or when it supports what we already do.

- tye        

In reply to Re^9: XML::Fling begone? (goals) by tye
in thread XML::Fling begone? by Aristotle

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.