Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59866
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CANVO1E1Z5Jn0EBi68qjMbSmHZYgjRAyZaTZcFkxF-PQQP0xFtQ@mail.gmail.com>
References: <CAF+90c_hj7PrWbm42dj0DhN7Ygmc=vckP=bcYfsVuod4=RrOQQ@mail.gmail.com>
 <1334271932.4609.161.camel@guybrush> <CANVO1E1Z5Jn0EBi68qjMbSmHZYgjRAyZaTZcFkxF-PQQP0xFtQ@mail.gmail.com>
Date: Fri, 13 Apr 2012 11:37:00 +0200
Message-ID: <CANVO1E2giwx4HGPZYO3XGi04H_8zok62Y9ujJ2jXAfxsv-ZfbQ@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=20cf303f6522194c8804bd8c38a5
Subject: Re: [PHP-DEV] Allow non-variable arguments to empty()
From: paul.konyves@gmail.com (Pal Konyves)

--20cf303f6522194c8804bd8c38a5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

> Hi!
>
> "The original reason for this restriction probably is that - in a way -
> it "doesn't make sense" to pass anything but a variable to empty()"
>
> I don't see the point of empty( function() ).
>
> You tipically use empty on values that holds information you want to use
> later in the program flow (a string, an integer). That means you'd better
> extract it to a variable because you want to avoid calling twice a functi=
on
> that provides this value.
>
> In my opinion, in other cases a 'isThatStuffTrueOrFalse()' function shoul=
d
> be created to provide the same information as empty( returnThatStuff() ).
> They both are yes-no questions, but the preceding one is a better
> indication what the program does.
>
> Pal
>
>
> 2012/4/13 Johannes Schl=C3=BCter <johannes@schlueters.de>
>
>> On Wed, 2012-04-11 at 00:53 +0200, Nikita Popov wrote:
>> >
>> > Currently the empty() language construct only works on variables. You
>> > can write if (empty($array)) but not empty if (empty(getSomeArray()).
>>
>> I've mentioned this thought off-list already but let's discuss it
>> officially:
>>
>> A fear I have is that this makes empty more looking like a function,
>> while not being one. Right now one notices quite quickly that it is
>> something else. Things like $check =3D $condition ? "empty" : "isset";
>> $check($bar); trigger an even more confusing error (Call to undefined
>> function)
>>
>> I'm not sure whether that's a strong argument, but I guess it's good
>> enough to be noted :-)
>>
>> johannes
>>
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>

--20cf303f6522194c8804bd8c38a5--