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" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
