Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82634 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70177 invoked from network); 13 Feb 2015 18:08:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Feb 2015 18:08:18 -0000 X-Host-Fingerprint: 79.94.237.143 143.237.94.79.rev.sfr.net Received: from [79.94.237.143] ([79.94.237.143:5979] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/26-40724-F8D3ED45 for ; Fri, 13 Feb 2015 13:08:16 -0500 Message-ID: To: internals@lists.php.net References: <54DDA797.4030501@php.net><1E15BAAB-C8FC-49A9-B73F-E0E7DEFA208D@ajf.me><54DDEAB6.1050107@php.net><008301d0478b$c060a5d0$4121f170$@tekwire.net> In-Reply-To: Date: Fri, 13 Feb 2015 19:07:59 +0100 Lines: 1 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 8bit Importance: Normal X-Newsreader: Microsoft Windows Live Mail 15.4.3555.308 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308 X-Posted-By: 79.94.237.143 Subject: Re: [PHP-DEV] [DISCUSSION] Make empty() a Variadic From: bensor987@neuf.fr ("Benoit Schildnecht") Hi, ""Sebastian B.-Hagensen"" a écrit dans le message de groupe de discussion : CAOjCV8yX7vOHTD1ja2oBDRntDZB0Q1SOYQdyhSaR3vt2vGSS+Q@mail.gmail.com... >2015-02-13 14:45 GMT+01:00 Thomas Punt : >> Hi Francois, >> >>> From: francois@tekwire.net> >>> May I suggest to extend your proposal to is_null() with the same logic ? >> If we were to do the same with is_null(), then would it not be best to do >> it with all the is_*() functions? I would be more than happy to cater for >> those functions as well, though their usages seem a lot less common. What >> does everyone else think? > While I don't know how common such a usage is I'm certain that there > is a use case for it. However, just modifying a subset of the is_* > functions sounds like a bad idea. If such a change is applied it > should be done to all type related is_* functions and be similar to > issets behavior (return false if at least one argument is not of the > given type). I agree, this behaviour should be extended to all the is_* functions if possible.