Re: Changing opened_path to being emalloc()'ed

My understanding is that it's like this since the PHP 3.0 times, where the memory manager was only available during requests, but not during module-startup. It should be completely fine today. Zeev At 22:36 30/08/2000, Andi Gutmans wrote:

Hi, Something which has been on my TODO for a loooooong time but I didn't do it because I wanted to wait for after 4.0.2. Does anyone see any reason for opened_path not to be emalloc()'ed? It's been like this for historic reasons and I haven't seen opened_path being used neither before nor after our memory manager is initialized/shutdown. So I want to change it all to emalloc()'s now so that we don't have leaks. Andi --- Andi Gutmans <andi@zend.com> http://www.zend.com/ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net

-- Zeev Suraski <zeev@zend.com> http://www.zend.com/