Re: New zend_compile.c to solve all of the duplicate function problems

From: Date: Thu, 18 Oct 2001 15:33:12 +0000
Subject: Re: New zend_compile.c to solve all of the duplicate function problems
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-68248@lists.php.net to get a copy of this message
BM>> include_once as i have already stated is useless inside of a BM>> function. Variables in the file are not global. And, I cannot Why include_once inside a function is different from include inside a function? BM>> include it again with include_once. The example I gave is not BM>> acurate to how we use it. We actually use a variable, not a BM>> define to control the inclusion of a file. Can you explain this further? How comes that include_once is not enough to prevent double include and ensure the function is defined? BM>> The other thing is that backward compatiblity was broken when it BM>> did not have to be. include_once is a *new* function in PHP to BM>> lots of people. There's a backward compatibility and there's a bug-compatibility. The PHP always worked so that you cannot redefine functions once defined (we'll leave ZE2 discussions about function ovverides alone for now). If there was a bug that allowed to do it, it's a logical thing to fix it, not to drag it through versions as if it should be so. -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115

« previous php.dev (#68248) next »