> Right, sorry, more precisely, by setting them to pemalloc/pefree they > result in calling malloc/free anyway. Not a direct mapping of course. > But I think we have beaten this one to death. Since PHP just calls > malloc/free anyway and the wrapper layer is causing problems, simply > removing the php layer is the obvious answer.
Yep. - Andrei -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
