The problem is backward compatiblity. That is the biggest thing at stake
here. Daniel and I are a bit skewed as we have over 1000 files full of code
that start with something like:
if(defined("_FILE_NAME")) return;
define("_FILE_NAME", 1);
This was our solution _before_ include_once ever existed to keep files from
being included more than once. We now know that it is in fact just not
executed.
Our hope is to keep the old behaviour in tact for these cases where it is a
valid solution. The patch I sent will now allow a function to be redeclared
ever, and it will raise an ERROR if the function is being declared in a
different location than it has alread been encountered.
Brian.
----- Original Message -----
From: "Edin Kadribasic" <[EMAIL PROTECTED]>
To: "Daniel Beckham" <[EMAIL PROTECTED]>
Cc: "PHP Development" <[EMAIL PROTECTED]>
Sent: Friday, October 19, 2001 9:27 AM
Subject: Re: [PHP-DEV] New zend_compile.c to solve all of the duplicate
function problems
> > By all means, if you have a decent proposal that doesn't involve
> exclusively
> > using include_once() or if/endif everywhere possible, we would love to
> hear
> > it.
>
> I'm just curious: what's wrong with using if/endif where include_once
isn't
> good enough?
>
>
> --
> 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]
