Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48902
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <97.C6.04713.A3B2F1C4@pb1.pair.com>
To: internals@lists.php.net
References: <AANLkTilEfGgHHqTv1YZu4yU6nse0t29UB7nlrnUDUwIO@mail.gmail.com> <AANLkTinvW2YBikeuy-LY8a2SdAU_AE-R73JCdpXIXDJ8@mail.gmail.com> <4C1EA662.1010601@sugarcrm.com> <49B64FA1-1BAA-4C88-AC9D-09E75792F05C@seancoates.com> <4C1ED20E.8050805@sugarcrm.com> <4C1ED846.90108@lerdorf.com> <4C1EDD54.6030109@sugarcrm.com> <1DA19859-F48E-403C-BC1B-53C72405D014@pooteeweet.org>
Date: Mon, 21 Jun 2010 13:04:54 +0400
Lines: 25
Subject: Re: [PHP-DEV] APC in trunk
From: dmda@yandex.ru ("jvlad")

>> 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.
>
> I understand that this effect is caused by the fact that APC destroys PHP 
> classes earlier than PHP engine otherwise would. You can claim it's a bug 
> but then until it's fixed enabling APC would still cause BC break, and no 
> amount of renaming this fact would change it.
> If we can fix it and make it work properly - fine, then this ojection 
> ceases to exist as soon as it's done, if there's no more cases when APC 
> behaves differently.
>
>
> I am still undecided if to enable by default, but originally
> the idea was to bundle with PHP 6, and I think this type
> of BC break in an edge feature (or rather edge bug) would be ok in a major 
> update to the language.

If I get it right, the BC break will depend on whether apc is enabled or 
not.
So, it's not major update brings the breach.

-jv