Re: Re[2]: [PHP-DEV] PHP 5.1
| From: | Ron Korving | Date: | Tue, 14 Jun 2005 14:14:51 +0000 |
| Subject: | Re: Re[2]: [PHP-DEV] PHP 5.1 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-16676@lists.php.net to get a copy of this message | ||
Personally, I doubt this is a problem.. I mean, how many ifsetor() variables
are we talking here? You call the function, so therefor the variable could
be set, otherwise you wouldn't be checking for it. In the case it was set,
it would've been in the symbol table anyway.
Ron
"Sven Fuchs" <svenfuchs@artweb-design.de> wrote in message
news:344317232.20050614161045@artweb-design.de...
> > This implementation of issetor() actually works fine, except it does
> > pollute the symbol tables with empty variables ($a and $b in this
> > examples are created, as nulls).
>
> What are the consequences of polluting the symbol tables this way?
> Should this issetor() be considered a "bad practice", probably for
> medium to large scale applications?
>
> --
> Sven