Re: PHP 5.1
| From: | Ron Korving | Date: | Tue, 14 Jun 2005 14:01:35 +0000 |
| Subject: | Re: PHP 5.1 | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-16673@lists.php.net to get a copy of this message | ||
Hi Zeev,
You're absolutely right.. How awful of me that I didn't see this coming.
Honestly, what's the point of having an ifsetor() in PHP, when people can
obviously write it themselves? Everybody wants a slighty different
implementation of an ifsetor(), ifnotemptyor(), coalesce(), etc... Why are
people wasting their breath on this? I figured it would be a good addition
to PHP at first, but seeing as everyone could write this in PHP themselves,
I really don't get the point.
Maybe it's the case that a lot of pro-ifsetor() people, are unaware (like I
was) of the fact that one really could implement a decent ifsetor()
themselves?
Ron
"Zeev Suraski" <zeev@zend.com> wrote in message
news:5.1.0.14.2.20050614165106.02a01c80@localhost...
> One is not supposed to be emitted either, variables passed by reference
> don't generate notices regardless of whether they exist or not, to allow
> returning data through them. 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).
>
> Zeev