RE: [PHP-DEV] Runtime-JIT, the whole enchilada
| From: | Andi Gutmans | Date: | Sat, 27 Jan 2007 17:19:01 +0000 |
| Subject: | RE: [PHP-DEV] Runtime-JIT, the whole enchilada | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-27690@lists.php.net to get a copy of this message | ||
Btw, having a request object was one of the #1 requests in framework :) People actually really like
encapsulating this because it
also makes unit testing easier down the road...
Just mentioning this because I don't think we should be too set with our ways esp. for people
who need to accomplish more
functionality.
Andi
> -----Original Message-----
> From: Pierre [mailto:pierre.php@gmail.com]
> Sent: Saturday, January 27, 2007 3:16 AM
> To: Andrei Zmievski
> Cc: Dmitry Stogov; Sara Golemon; internals@lists.php.net;
> Andi Gutmans; Zeev Suraski; Stanislav Malyshev
> Subject: Re: [PHP-DEV] Runtime-JIT, the whole enchilada
>
> Hello Andrei,
>
> On 1/27/07, Andrei Zmievski <andrei@gravitonic.com> wrote:
> > Good luck trying to retrain millions of programmers to use a CGI
> > object or a function to retrieve GPC values.
>
> You will be surprised, really :)
>
> > Really, how much of a
> > performance hit is Sara's patch going to be, compared to
> other things
> > in PHP 6?
>
> It is to early to argue about performance problems in my
> humble opinion. My point was more about the complexity.
> That's why I prefer the other solution which simply moves the
> JIT to runtime without other changes but a function to get
> the encoding error.
>
> To be honest, I do not understand the resistance to commit
> experimental code in head. For what really matters, we need a
> working solution. It does not need to be perfert, it needs to
> work (more or less). We still have plenty of time to improve
> it until 6 is out (not going to happen in the next months anyway).
>
> --Pierre
>