Hi!
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.
apc.file_update_protection could have some unexpected results too.
Not any that change the behaviour of PHP.
Do I misunderstand how this feature works? I was under impression that
it prevents APC from updating the file for X seconds since its
modification - while plain PHP of course would see the change instantly.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
