Hello,
just a quick question - will the include_once() (Optimized require_once()
and include_once() by eliminating fopen(3) on second usage. (Dmitry))
optimisation fix in 5.2.0 backported also in PHP 4 tree (in 4.4.5 maybe?)
Theoretically speaking (havent checked the default funcs internal changes
between 4.x and 5.2) could it be possible to patch 4.x without breaking the
rest of the core?
rr
Hello,
just a quick question - will the include_once() (Optimized require_once() and
include_once() by eliminating fopen(3) on second usage. (Dmitry)) optimisation
fix in 5.2.0 backported also in PHP 4 tree (in 4.4.5 maybe?)
No, no features will be back ported to PHP 4.4.
regards,
Derick
No, no features will be back ported to PHP 4.4.
Although I dont see this as feature more like a fix (uneeded opens() stats()
on each call) still thank you for the fast reply.
p.s. lately the topics and discussions on internal list are pretty scarry..
starting with political issues and ending with memory manager flaws (besides
also some phparchitect articles which propose/show 5.2 being faster in all
generic tests still slower in realworld aplications).. which probably makes
a lot (at least me) users uneasy about switching to the 5.2.x tree :)
rr
Reinis Rozitis wrote:
p.s. lately the topics and discussions on internal list are pretty
scarry.. starting with political issues and ending with memory manager
flaws (besides also some phparchitect articles which propose/show 5.2
being faster in all generic tests still slower in realworld
aplications).. which probably makes a lot (at least me) users uneasy
about switching to the 5.2.x tree :)
If you were using PHP 3, you could have made the same argument probably.
Its not a perfect process. It gets ugly sometimes. But, IMO, it
works better than one or two people having total control and say in how
things are done.
--
Brian Moon
http://dealnews.com/
It's good to be cheap =)