Re: New zend_compile.c to solve all of the duplicate function problems
| From: | Zeev Suraski | Date: | Sun, 21 Oct 2001 08:34:09 +0000 |
| Subject: | Re: New zend_compile.c to solve all of the duplicate function problems | ||
| References: | 1 2 3 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-68589@lists.php.net to get a copy of this message | ||
Yeah, ok, but that's what I'm getting at. What if we add a directive that makes all of the files on your site (or for that matter, in a certain directory) treat include as include_once?
At 06:31 21-10-01, Daniel Beckham wrote:
Intentionally? No, not really, but two seperate code files could include a single basic function library that both need seperately, but as soon as those two original code files are included into a main script of some sort, that basic function library is now being included twice. Daniel ----- Original Message ----- From: "Zeev Suraski" <zeev@zend.com> To: "Brian Moon" <brianm@dealnews.com> Cc: "Edin Kadribasic" <edink@proventum.net>; <php-dev@lists.php.net> Sent: Saturday, October 20, 2001 8:42 PM Subject: Re: [PHP-DEV] New zend_compile.c to solve all of the duplicate function problems At 19:11 19-10-01, Brian Moon wrote:it- Even with no protection at all, function redefinitions will not be reported. That's kind of ugly.An E_NOTICE is raised at runtime. I know many people ignore these, butis there.So basically, your existing code base will now be issuing tons of E_NOTICE's? How about if we introduce an implicit _once directive? Do you have cases in which you intentionally include the same file twice? Zeev -- 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