Re^23: Is an aXML compiler possible?

[ikegami]

Saying that I need to declare dependency on a plugin from the standard set is like saying that I need to predeclare the use of standard keywords in perl;

Exactly. Up until this point, you said we had to do this:

use my;   # Because Some::Plugin needs it.
use for;  # Because Some::Plugin needs it.
use Some::Plugin;

Like you said, it's nonsense.

But it looks like you just changed your story again!

Are you now saying that &lab; is standard and will always work out of the box?

Are you now saying that <post_include>common/lab</post_include> is standard and will always work out of the box?

Previously, you said they weren't. Where can I find aXML to test this?

[Logicus]

I never said you needed to do anything of the sort.

As for the specials, prior to you isolating the example of needing them in those rare special cases, I had never really paid them much attention or even felt any need to. The e-commerce site didn't need to output aXML (or perl code), neither did the auctions site, or the forum system.

I find it rather bizarre your so fixated with them, since they are such a rarely needed thing in real world applications.

However having said that I do recognise that for the solution to be absolutely complete that there needs to be a standardised solution to this, such that PerlNights will be able to input, store and output absolutely any string, even strings containing the specials themselves.

When I'm completely happy that I have an infallable solution to it I will document it properly and you will have a static final answer, until then and until the new version is finished complete with said solution, whatever is said about it is subject to change if or when a fault is found, or even if I change my mind about it. (my perogative, my language)

Note; the problem and solution exist at the level of the perl and the plugins, not at the level of the aXML document, and any criticism that is levelled along these lines is a criticism of the perl implementation of aXML and not of aXML itself.

The version I have at the moment is capable of outputting long and complex aXML strings correctly, and even source highlighting them (wanna see a screen shot?). But when it comes to outputting Perl code, specifically, and only, Perl code which uses the specials, it breaks and I'm currently working on that issue, rare as it is, because I want the implementation to be 100% perfect, not merely 99.99999% perfect.

So unless your going to tell me that it is impossible to solve the problem, (ie, that Perl itself cannot do it) then perhaps it would be more useful to focus on something else until I have fully solved it? If you are going to tell me it's impossible, then I'm sorry but I'm not just going to take your word for it until I have fully exhausted every trick I can think of to do so. (such is my faith in Larry)

If I do find out it's totally impossible, the ketchup bottle will be fetched from the fridge, and I will be offline for a while with a severe stomach ache.

[ikegami]

You didn't answer my questions.

Are you now saying that &lab; is standard and will always work out of the box?

Are you now saying that <post_include>common/lab</post_include> is standard and will always work out of the box?

Where can I find aXML to test this?

I find it rather bizarre your so fixated with them, since they are such a rarely needed thing in real world applications.

We know you're a bad coder, but you don't have to brag about it. Finding out how to escape is the first one needs to figure out how to do when writing a plugin. That is in no way rare!

Note; the problem and solution exist at the level of the perl and the plugins,

It doesn't matter how many times you say it, it's not going to be true until the answer to my first two questions becomes "yes".

The version I have at the moment is capable of outputting long and complex aXML strings correctly

No, a plugin can't do that until the answer to my first two questions becomes "yes".

(You keep countering claims about what a plugin can do to claims about what aXML can do. I'm going to assume it's just a mistake on your part rather than a lie by misdirection.)