in reply to Re^9: Is an aXML compiler possible?
in thread Is an aXML compiler possible?

>Don't make excuses; fix it.

Why should I bother... I don't need a compiler for it since now I'm using Plack, the processing cost per page rendered has been reduced by such an amazing amount that even my $20 a month dev server is sufficient to get me started. (and I have that typical lazy-ass perl programmer gene)

I ask if a compiler is possible for intellectual reasons and because I've heard both that it can be compiled and that it cannot be compiled from two people who are apparently highly respected. One of you is wrong, and I know who my money is on.

As for your code examples, I really have no idea what the problem is with that, and why you feel that the delimiter chars need constricting in some way. I've never needed any such constrictions and I don't believe anyone else needs them either!

Perhaps the way aXML really works will become clearer to you once I have finished working on PerlNights.com and you can download the complete source-code for it. I'm 6 days into the project now, and I've nearly finished replicating the bulk of PerlMonks feature set.

It wouldn't of even taken that long if I didn't have to take some time out to help my Mum organise her furniture and stuff now that we have just moved again, and also I had to spend a few hours fixing a very subtle bug in the parser, but that's sorted now and I have dozens of aXML docs now rendering correctly.

The standard plugin set aXML::Engine is currently 915 lines of code, a few hundred of which have also been written in the last few days taking up some of the site development time.

As for comparing aXML to TT, your right it's not a fair comparison, aXML is infinitely superior, as you will see soon enough.

Replies are listed 'Best First'.
Re^11: Is an aXML compiler possible?
by ikegami (Patriarch) on Oct 30, 2011 at 21:07 UTC

    Why should I bother...

    Wrong tense. You did bother working on it. Why are you asking me what your reasons were?

      Correct Tense.

      I worked on a compiler because that's what Corion suggested I do. That was the reason behind the "too difficult for me" thread where I made it clear that I was struggling to write such a compiler, and did not believe I was capable of doing so alone without help. That was prior to finding out about Plack, and optimising the runtime parser, thus obviating the need for a compiler given the sheer speed of modern server hardware.

      That particular wild goose chase cost me a good couple of months development time, and I'm not inclined to persue it further in light of the current speed of the new parser which is well fast enough for my uses.

      If after I have proven the value of aXML to the masses, someone feels like creating a compiler for it then they are free to do so, however I will not be bothering as I really have better things to do.

        I worked on a compiler because that's what Corion suggested I do.

        The distinction between compilation and interpretation is orthogonal to the ability to write a BNF (or another specification) of the language's syntax. Compilation versus interpretation is a detail of implementation.

        What ikegami is trying to understand is if there are legitimate documents you cannot produce from aXML programs because they contain character sequences that could be aXML instructions. (Certainly you can modify the plugin environment to avoid that, but there's a tarpit to avoid in doing so. Whether that's a problem in practice is up to the user to discover, but I've worked around quoting issues in polylingual programs before and have no inclination to do so again.)


        Improve your skills with Modern Perl: the free book.

        A reply falls below the community's threshold of quality. You may see it by logging in.

        Correct Tense. I worked on a compiler because that's what Corion suggested I do

        So which one is it? You didn't bother, or the reason your bothered is that Corion suggested you do it?