Richard,
zval is such a common PHP structure that in a scope of a single script
(even a trivial one) you'd have thousands of them. Therefor even an
extra 4 bytes matter, and for people with large application it would
matter even more. I wish the patch was such that it had no impact on
the people who don't need it, but the reality is that for anyone who
does not need gc cycles, it'll be a performance (speed & memory)
penalty. This is why I had intimately suggested making it a compile
time, configuration option.
On 7-Dec-07, at 9:25 PM, Richard Lynch wrote:
On Tue, December 4, 2007 2:18 pm, Rasmus Lerdorf wrote:
Stanislav Malyshev wrote:
1. Always compile it in but leave undocumented #ifdefs in place for
performance freaks. Those same performance freaks aren't going to
care
about the binary compatibility issue since they are the same people
who
build all their own stuff.
Note that breaking BC is not only about performance - one your build
is
not the same as mainstream PHP, you can't use any binary extension
which
would do anything non-performance-related - like interfacing some
external system/library, debugging, profiling, testing, security and
so on.
Any commercial module won't be available for the user of this
switch,
and all open-source modules one'd have to build by oneself, which
may be
serious maintenance issue. I know there are a bunch of companies
that
compile PHP with their own options but still use commercial modules,
including both performance and non-performance ones. They couldn't
use
this compile switch.
Yes, I know what binary compatibility means.
Call me crazy, but...
Would it be possible to hard-code the bit that adds the 4 bytes to the
zval, but make the execution bit a flag so that binary compatibility
is always there, but the executable code that does the GC can come or
go as needed?...
Or am I just talking nonsense due to ignorance?
--
Some people have a "gift" link here.
Know what I want?
I want you to buy a CD from some indie artist.
http://cdbaby.com/from/lynch
Yeah, I get a buck. So?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Ilia Alshanetsky
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
