Stanislav Malyshev wrote:I'm concerned that this problem of breaking common platform might be more dangerous than the performance benefit. Which, BTW, I estmate as pretty minimal - code space is shared on all modern OSes anyway, so a little
I think that's a good point for leaving it the way it is: Minimal benefit while opening a can of worms of possible problems.
Another reason not to do it is the amount of work to decide which function should go where. Let's keep it simple and focus on IMHO more pressing problems.
Guys,
You are all missing the point. All the ext/standard would still be enabled by default, but it would allow people with very high traffic sites who need to save every bit of memory they can to build a lean-and-mean version of PHP.
These kinds of users are looking for optimizing PHP for their application and do it with a sane mind.
I don't even mind if --disable-all doesn't disable ext/standard but it'd be nice that if we do a split to core/ and standard/ (I wouldn't go into more granularity than that) that we could have a --disable-standard.
It wouldn't hurt anyone and it *is* a pressing problem from talks I've had with all sorts of ppl that have high traffic machines.
No one answered me about regex btw. Is it only being compiled because of the regex functions in ext/standard or does anyone know if other places in PHP's source tree use it.
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
