in reply to Re^34: aXML vs TT2
in thread aXML vs TT2

I'm confused. Were my efforts misguided and cause no change, or did you add the special chars?

On the subject of the compilers, I told Corion about 3 months ago that I believed aXML could not be compiled, he insisted it could, now your telling me it cannot, one of the 3 of us must be wrong.

Well, the template can be compiled. The problem is that the plugins all return template code, and those can't be compiled, and that's where the real slow down is.

I'm sure Corion didn't know that your plugins all returned template code.

it works perfectly well as it is doing what it does.

You're wrong. You know you're wrong because you're just tried to fix the problem in response to this thread. It may work perfectly well at what *you use it for*, but the only way that can be true is if you use a tiny subset of the functionality you make very clear that it has (the ability to output any format). So in other words, the fact that you've used it successfully is completely irrelevant.

If it works perfectly well, the answer to Re^33: aXML vs TT2 should be trivial. Please answer it.

Replies are listed 'Best First'.
Re^36: aXML vs TT2
by Logicus (Initiate) on Oct 24, 2011 at 00:52 UTC

    I want to start by saying your efforts are very much appreciated, whether they ultimately turn out to be fruitful or not.

    Yes, you have caused the addition of 2 extra lines of code, and a standardisation of the now 6 specials.

    But, no, I've never needed these things before and they seem to be a symptom of having to deal with non-aXML compliant code and it's related issues rather than anything actually wrong with aXML itself.

    Yes, Corion said that the return values should also be compiled as well, which is where I lost him because I can't think of anyway to know ahead of time what a given tag is going to return. Hence I'm with you on your side of that debate, and I have a feeling that following Corion's suggestion to write a compiler for it may of been a wild goose chase and a waste of about 2 months worth of programming time on my part.

    However, having said that somehow Perl does manage to execute the aXML code correctly so it must be compiling it in some manner prior to doing that.

[reply]

      However, having said that somehow Perl does manage to execute the aXML code correctly so it must be compiling it in some manner prior to doing that.

      Perl does not execute any aXML code at all. It executes the code of your parser and plugins. Your parser interprets the aXML code.

[reply]

        Ok that makes sense yeh. Perl interprets the code of the engine, and builds a compiled system out of it capable of interpretting both aXML and Perl. You know what that means?

        As far as I can tell, Perl 5 code gets interpretted and compiled into Perl 4 code, which gets interpetted and compiled into Perl 3 code and so on down to Perl 1 then Opcodes then machine code.

        So if aXML was written in Perl 6 instead of Perl 5, and my name happened to be "Larry Wall".. instead of dealing with some unknown bolshe troll guy who no one has ever heard of, you would be getting all excited about being involved with the groundwork of "Perl 7".

        No?

[reply]

In Section Meditations