Re: APC in trunk
| From: | Rasmus Lerdorf | Date: | Mon, 21 Jun 2010 03:11:02 +0000 |
| Subject: | Re: APC in trunk | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-48878@lists.php.net to get a copy of this message | ||
On 6/20/10 7:44 PM, Stas Malyshev wrote:
> Hi!
>
>> Can you elaborate? What "average user"-facing features are non-obvious?
>> We should document them if nothing else.
>
> This recently caught my attention:
> http://pecl.php.net/bugs/bug.php?id=16745
> As I understood from this bug, APC changes how PHP works (since it works
> without APC but not with it) and it is not considered a problem in APC.
> Which means enabling APC by default is a BC break, and there's already a
> proof that it breaks real-life code (even if particular code had been
> changed to work with it, the fact that APC can break otherwise working
> code stays). Now probably most of the experienced users wouldn't mind
> fixing the code a bit, but for enabling by default it should be 100% BC.
This is an unfixed PHP bug. There have been a number of threads about
the object destruction order on internals. It isn't just APC that is
affected by this. Other extensions are affected as well.
> apc.file_update_protection could have some unexpected results too.
Not any that change the behaviour of PHP.
-Rasmus