This feature was described as "experimental" in the documentation. Maybe the "experiment" didn't work out - or it worked out fine and equivalent optimizations are part of the normal compliation of PHP code now?
I would hope the latter - it doesn't seem like a bytecode cache should have to do optimizations; that would be the compiler's job and would benefit everyone regardless of which cache they use. Sensible factoring would not blur the roles of those two components. But I haven't delved into the source to find out what this option really did (: On Sat, Dec 3, 2011 at 11:04 AM, Dmitri Snytkine <dsnytk...@ultralogistics.com> wrote: > The option apc.optimization has been removed in apc 3.0.13 > I wonder if there are any plans to put the code optimization option back > into APC, so the APC will be not only the cache of php files but also act as > an accelerator? > > > > Dmitri Snytkine > Web Developer > Ultra Logistics, Inc. > Phone: (888) 220-4640 x 2097 > Fax: (888) 795-6642 > E-Mail: dsnytk...@ultralogistics.com > Web: www.ultralogistics.com > > "A Top 100 Logistics I.T. Provider in 2011" > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
