>> 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
