I'm not ignoring anything!

My attitude is this, in 2007 I wanted to write a compiler for aXML because I felt that the code was too slow and needed speeding up. 4 years down the line, I still think it's a bit on the slow side, but improvements I have managed to make on my own in my uneducated ignorance + the action of moores law has almost (but not quite) obviated the problem to a point where I am now wondering if it is really worth sacrificing certain dynamic aspects of aXML in order to make it faster, given that we are late game on a very steep upward exponential curve of available processing power.

Right now, in 2011, if aXML was to be used for a large site a compiler would be needed and it would be best done using something along the lines of H.O.P, however if I was to abscond again for another 4 years and to come back here in 2015, or 2019, I doubt that such a thing would be needed anymore for even massive sites since the amount of raw computing power available at that time will be just ridiculous.

Oh btw, various suggestions made by kind people around here have helped me shave about 5% off the parsing overhead by eliminating things that I added in because I thought they were "better perl" such as $&.

In reply to Re^7: rough start of an axml compiler by Logicus
in thread rough start of an axml compiler by Logicus

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.