Re: compiler in php..
| From: | Aric Caley | Date: | Mon, 19 May 2003 23:18:45 +0000 |
| Subject: | Re: compiler in php.. | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-148230@lists.php.net to get a copy of this message | ||
I always enjoy getting a reaction, positive or negative..
Considering its a really simple "language" I don't see why it would be all
that slow. There are templating engines that have pretty much full blown
internal languages so I dont see it being any slower than those. I dont
wish to start a war over template engines, but I've looked at things like
smarty, with full blown programming -- functions, variables, loops, etc.
What I'm proposing is actualy simpler. Yeah, if you really used the frame
programming concept to the max, you might end up with more files and more
overhead, but I dont see it really being that much worse. I see php
applications already that need to load dozens of files, parse multiple
templates and config files, not to mention SQL queries...
Naturaly, on a production server, you'd have the resulting code cached; or
you'd run the compiler once and upload the result only. I'm just saying
having it run automaticaly as part of the script would be convenient when
developing since you dont have to compile PHP code. At some point it may
very well make sense to have a C program do it. Or perhaps a PHP
extension/module?
"Rasmus Lerdorf" <rasmus@lerdorf.com> wrote in message
news:Pine.LNX.4.44.0305191545470.1158-100000@thinkpad.lerdorf.com...
> On Mon, 19 May 2003, Aric Caley wrote:
> > (and for those curious what I'm doing, I'm trying to make a Frame
Processor
> > for PHP, as described in the book "Framing Software Reuse". I want it
to
> > run dynamicaly so you dont have to add a compile step.)
>
> That's nuts! Do you have any idea how slow that would be?
>
> -Rasmus
>