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" <[EMAIL PROTECTED]> >To: "Brian Moon" <[EMAIL PROTECTED]> >Cc: "Edin Kadribasic" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> >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: > > > > - 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, but >it > > >is 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: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > To contact the list administrators, e-mail: [EMAIL PROTECTED] > > > > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
