Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75214
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <alpine.LNX.0.999.1407031108350.526@swan.dds.nl>
References: <alpine.LNX.0.999.1407031108350.526@swan.dds.nl>
Date: Thu, 3 Jul 2014 13:10:40 +0200
Message-ID: <CAMyk_AZJx3UuX3WfMcuw0dtHVOt66xJLueJJt+MZyNXy-AR8iw@mail.gmail.com>
To: Xen <xen@dds.nl>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1134d88269623104fd481072
Subject: Re: [PHP-DEV] not_null function
From: linepogl@gmail.com (Lazare Inepologlou)

--001a1134d88269623104fd481072
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2014-07-03 11:40 GMT+02:00 Xen <xen@dds.nl>:

> Heya,
>
> I was just wondering about something.
>
> It seems way more natural and flowing to have and use a "not_null"
> function in addition to some "is_null" that currently exists.
>
> The reason is that most of the time you are not checking null condition,
> you are really checking the non-null condition.
>
>
Well, there is a better alternative:

if ( $x =3D=3D=3D null ) ....
if ( $x !=3D=3D null ) ....

This syntax has also the advantage that it is marginally faster as there is
neither a function call nor a negation involved.
:)


Lazare INEPOLOGLOU
Ing=C3=A9nieur Logiciel

--001a1134d88269623104fd481072--