[EMAIL PROTECTED] wrote: > I think having it configurable is a must. Turning it on / off via a compile > flag will not suit everyone.
Looking at the code, that isn't really possible. You could have a switch to turn off the collection, but that won't get you your performance back. To avoid the performance penalty you need it to be a compile-time decision. I only see 2 possible workable solutions here: 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. 2. Drop it -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php