The point is that it would be there for people to use, with as little effort as possible, which would be changing 1 byte inside the INI file. The issues APC is having with certain code is not specific to APC, and does happen with other open source caches. Perhaps we need to examine the validity of that code, or simply not cache the code that's affected.
On Sun, Jun 20, 2010 at 11:19 PM, Stas Malyshev <smalys...@sugarcrm.com> wrote: > Hi! > >> Even if the extension is compiled by default, we can (and probably >> should) leave apc.enabled at Off, recognizing some the things you are >> mentioning. > > I'm not sure I see the point of compiling it if it's disabled. Anyway, most > of the distributions probably would make it .so just as it happens now for > tons of other modules and would enable it in .ini. And building it from > source you almost never rely on defaults anyway if you know what you want > (which is the reason why you didn't use the binary one, I guess). So, > summarily, I don't think we should enable it by default, as for compiling it > by default, I don't think it matters too much since I don't believe defaults > matter too much there. > -- > 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
