The thing I don't like about this sort of approach, even if it was done with a lovely modern H.O.P lexer or whatever, is that it fundamentally breaks several of my plugins which exploit the runtime parsing engine to do cool things like the refas.
I really can't be bothered carrying on with this, you can moan about how wasteful of processor time my method is all you want, and how it can't be streamparsed, and how its a non-context-grammar-free-lispish-whatever... it doesn't detract from the coolness of aXML and how quick and easy it is to make complex sites with. I just can't be bothered trying to shave a few more clock ticks from the parser or write a compiler which breaks the way it works especially when the database connection even using Apache::DBI configured in the httpd.conf file takes far more processor time up than the parsing.
Bottom line is that this system is not that slow, it can do 30 requests a second running from a 5 year old 1.8ghz laptop, apache2 can use multi-cores, and I am confident that moores law will continue unabated for at least another 20 years so all in all I think my time would be better spent writing cool new plugins and deploying new sites with the existing parsing system that works more or less exactly as it did way back in 2007.
aXML and my parser are completely free for anyone to download and use for whatever they want to use it for and has been available, almost completely unnoticed, right here on perlmonks for the last 4 years.
If anyone feels like packaging it up for putting on CPAN then go right ahead, I have more interesting things to be doing :)
In reply to Re: rough start of an axml compiler
by Logicus
in thread rough start of an axml compiler
by Logicus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |