Hi Stefan,
I suggest you to remove words like 'discussion' from the wiki,
Hi Marcus,
-Original Message-
From: Marcus Boerger [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 9:27 PM
To: Dmitry Stogov
Cc: Andi Gutmans; Stas Malyshev; phpxcache; internals@lists.php.net
Subject: Re: [PHP-DEV] Patch for opcode caches
Hello Dmitry,
Monday,
On Fri, Mar 14, 2008 at 9:46 AM, Dmitry Stogov [EMAIL PROTECTED] wrote:
Removing early-binding at all might be a subject for PHP6, however in
PHP_5_3 we even keep ze1_compatibility_mode.
http://news.php.net/php.internals/36085
-Hannes
--
PHP Internals - PHP Runtime Development Mailing
On Fri, Mar 14, 2008 at 11:06 AM, Hannes Magnusson
[EMAIL PROTECTED] wrote:
On Fri, Mar 14, 2008 at 9:46 AM, Dmitry Stogov [EMAIL PROTECTED] wrote:
Removing early-binding at all might be a subject for PHP6, however in
PHP_5_3 we even keep ze1_compatibility_mode.
On Fri, 14 Mar 2008, Dmitry Stogov wrote:
however in
PHP_5_3 we even keep ze1_compatibility_mode.
I'm not able to remove it.
WHy not? It's quite broken anyway.
Derick
--
Derick Rethans
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
--
PHP Internals - PHP Runtime
Hello Dmitry,
Friday, March 14, 2008, 9:46:41 AM, you wrote:
Hi Marcus,
-Original Message-
From: Marcus Boerger [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 9:27 PM
To: Dmitry Stogov
Cc: Andi Gutmans; Stas Malyshev; phpxcache; internals@lists.php.net
Subject: Re:
Hello Pierre,
it is unused code that does not work as intended and causes trouble. And
at leats it makes maintanance harder. So that is a very big reason to drop
it.
marcus
Friday, March 14, 2008, 11:11:06 AM, you wrote:
On Fri, Mar 14, 2008 at 11:06 AM, Hannes Magnusson
[EMAIL PROTECTED]
On Fri, Mar 14, 2008 at 4:22 PM, Marcus Boerger [EMAIL PROTECTED] wrote:
Hello Pierre,
it is unused code that does not work as intended and causes trouble. And
at leats it makes maintanance harder. So that is a very big reason to drop
it.
Yes, I fully agree (you may have missed the not
I do not want to remove early binding. In fact I always
wanted to have early binding as much as possible. Because
that is faster and makes compiler caches easier. So why slow
down stuff? A Compiler cache wants everythign as static as
possible which means a compiler cache wants early
Hello Dmitry,
Friday, March 14, 2008, 5:08:18 PM, you wrote:
I do not want to remove early binding. In fact I always
wanted to have early binding as much as possible. Because
that is faster and makes compiler caches easier. So why slow
down stuff? A Compiler cache wants everythign as
But that means we are compiling inheritance when a file is loaded form
the cache. The goal should be to compiling inheritance when writing to
the opcode cache file. All we achieve here is a slow down. If there is
You can not do that. You do not know that until runtime.
something that makes
Hello Stanislav,
Friday, March 14, 2008, 5:51:49 PM, you wrote:
But that means we are compiling inheritance when a file is loaded form
the cache. The goal should be to compiling inheritance when writing to
the opcode cache file. All we achieve here is a slow down. If there is
You can not do
Hello Pierre,
yep, stupid me. I got confused by your wording :-)
marcus
Friday, March 14, 2008, 4:42:32 PM, you wrote:
On Fri, Mar 14, 2008 at 4:22 PM, Marcus Boerger [EMAIL PROTECTED] wrote:
Hello Pierre,
it is unused code that does not work as intended and causes trouble. And
at
Marcus Boerger wrote:
Hello Stanislav,
Friday, March 14, 2008, 5:51:49 PM, you wrote:
But that means we are compiling inheritance when a file is loaded form
the cache. The goal should be to compiling inheritance when writing to
the opcode cache file. All we achieve here is a slow down. If
Hello Stanislav,
Friday, March 14, 2008, 6:48:52 PM, you wrote:
Hi!
Lemme just think, doing inheritance at compile time before we send the stuff
to an opcode cache can be slower then? How is that possible? After all late
binding means we do it at run time. And no matter how much faster we
I don't actually see early binding as being much of a problem, the real
problem is when the same class is both early and late bound. If you
consistently always bind early or always bind late, opcode caches should
be quite happy to let you do that. But if you mix the two, things get
That's
16 matches
Mail list logo
