Re: [RFC] Allow non-variable arguments to empty() and isset()
| From: | Nikita Popov | Date: | Fri, 13 Apr 2012 12:12:19 +0000 |
| Subject: | Re: [RFC] Allow non-variable arguments to empty() and isset() | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-59874@lists.php.net to get a copy of this message | ||
On Fri, Apr 13, 2012 at 12:42 AM, Galen Wright-Watson
<ww.galen@gmail.com> wrote:
> Just to be clear, under the new behavior, calling "empty" or "isset" on
> undefined variables and undefined array indices shouldn't produce a notice
> when E_NOTICE is set, correct? Basically, the change isn't regressive.
Yup, that's right. So the change is BC-safe :)
> If this is so, how about adding appropriate regression
> tests to empty_with_expr.phpt and empty_with_isset.phpt?
The normal empty()/isset() behavior (including the suppression of the
notice) is tested in a few other tests, that's why I didn't add
additional tests for it there :)
Nikita