Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23158 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56460 invoked by uid 1010); 5 May 2006 03:41:54 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 56445 invoked from network); 5 May 2006 03:41:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 May 2006 03:41:54 -0000 X-PHP-List-Original-Sender: brianm@dealnews.com X-Host-Fingerprint: 129.41.69.185 smtp.dealnews.com Linux 2.5 (sometimes 2.4) (4) Received: from ([129.41.69.185:47521] helo=smtp.dealnews.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 8F/A8-63443-189CA544 for ; Thu, 04 May 2006 23:41:54 -0400 Received: (qmail 17320 invoked from network); 4 May 2006 23:41:47 -0400 Received: from unknown (HELO ?10.1.6.4?) (10.1.6.4) by 10.1.1.24 with SMTP; 4 May 2006 23:41:47 -0400 Message-ID: <445AC959.4090306@dealnews.com> Date: Thu, 04 May 2006 22:41:13 -0500 User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060406) MIME-Version: 1.0 To: Jared White CC: internals@lists.php.net References: <44584619.60400@lorenso.com> <200605030815.34801.johannes@php.net> <44585828.1030603@vocalspace.com> <44585E89.6000400@vocalspace.com> <44586BDF.6040600@developersdesk.com> <4459410D.9090802@vocalspace.com> <445942E9.201@developersdesk.com> <44594553.6020009@iamjochem.com> <44594A27.4040201@vocalspace.com> <4459558D.7050703@lerdorf.com> <445959DD.9030607@vocalspace.com> <44595F95.6090607@lerdorf.com> <445A558D.1070102@vocalspace.com> <20060504230604.7a2fe5e0@localhost.localdomain> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Seeking 'coalesce' php internal function From: brianm@dealnews.com (Brian Moon) > Well, from where I'm setting, Dante has brought up excellent points that > were never covered before according to my look at the list archives. In > fact, I find this situation indicative of a larger problem, which is > that extremely important discussions of major issues with the language > get breezed by far too quickly just because someone decides it's not > interesting enough or it's time to move on (*cough* named parameters > *cough*). I think the concept behind filled() is sound, has merit, and > is worth talking about seriously. > > Jared +1 Dante's discussion has nothing to do with ifsetor() or the filter extension IMO. Brian Moon dealnews.com