Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13414 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56848 invoked by uid 1010); 20 Oct 2004 11:13:21 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 56823 invoked by uid 1007); 20 Oct 2004 11:13:21 -0000 Message-ID: <20041020111321.56801.qmail@pb1.pair.com> To: internals@lists.php.net References: <20041020110454.29582.qmail@pb1.pair.com> Date: Wed, 20 Oct 2004 13:13:01 +0200 Lines: 28 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Posted-By: 62.58.68.2 Subject: Re: [PHP-DEV] suggestion: empty() with infinite parameters like isset() From: r.korving@xit.nl ("Ron Korving") Okay, I don't wanna make remarks that may have already been made earlier, but I think it should be "all should be empty", because it works exactly the same for isset(), and apparently, a decision was made to give isset() that feature. Ron "Derick Rethans" schreef in bericht news:Pine.LNX.4.58.0410201307210.1991@localhost... > On Wed, 20 Oct 2004, Ron Korving wrote: > > > I think it would be a good idea to apply the idea of infinite parameters > > that's been used with isset(), so one can test multiple variables: > > > > if (empty($var1, $var2, $var3)) echo "data missing"; > > We discussed this before and we didn't want to agree if it should behave > like "each one should be empty" or "all should be empty". So we will not > add it. > > Derick > > -- > Derick Rethans > http://derickrethans.nl | http://ez.no | http://xdebug.org