On 20 September 2015 00:29:48 BST, Lester Caine wrote:
>> The notices emitted by is_null are COMPLETELY IRRELEVANT.
>
>? is_null returns true if the variable exists and is NULL and throws a
>notice if the variable is not set WHY is that fact COMPLETELY
>IRRELEVANT?
is_null returns true in all the
On 20 September 2015 01:43:06 BST, Ryan Pallas wrote:
>I would also point out that is_null returns true (after the engine
>produces
>a notice) for undefined variables:
>
>$ php -r "var_dump(is_null($a));"
>
>Notice: Undefined variable: a in Command line code on line 1
>
>Call Stack:
> 0.0001
On 20/09/15 15:05, Rowan Collins wrote:
> is_null returns true in all the same situations as isset does. There is
> absolutely no difference except for whether it raises a notice.
? is_null returns true when isset returns false ... but because of the
notice and switching that off to hide it I'd
On 20 September 2015 17:10:23 BST, Lester Caine wrote:
>On 20/09/15 15:05, Rowan Collins wrote:
>> is_null returns true in all the same situations as isset does. There
>is absolutely no difference except for whether it raises a notice.
>
>? is_null returns true when isset returns false ...
Sorr
Hi Anatol and Ferenc,
On Sat, Sep 19, 2015 at 7:15 AM, Kalle Sommer Nielsen wrote:
> I'm sorry I have not caught this any earlier, but even without
> consulting with Anatol, I'm not keen on adding this into 7.0, we are
> in RC stage, and I want us to focus on a stable release instead of
> adding
