Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51986
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain yahoo.com.au from 98.139.91.210 cause and error)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com.au;
  h=DKIM-Signature:Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
  b=cLk8qoHxsijN8FDwQH1krnz8kx53Dtc1BmKYjC8sdp9hneGdfcFhlT4WgWx86lgzDOqqUygpW5o1S4UoP0aXLb4V+ZaJOlnLRFGi2AcJH9g1Gms3vaM7S41ga2JIkmywL+dIpwZmNZRHKzmAxWQqXdO2Bd59RXWstbvvxDg83bw=  ;
Message-ID: <4DB23F50.4090405@yahoo.com.au>
Date: Sat, 23 Apr 2011 12:54:08 +1000
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 ThunderBrowse/3.3.5
MIME-Version: 1.0
To: internals@lists.php.net
References: <AANLkTiknomAsTrsZ140rWs6CwxJP3UYGUokQbERhDiRp@mail.gmail.com>	<BANLkTi=LvYLaOoGgrzrWfYbQ+t9Wzv_XeQ@mail.gmail.com>	<BANLkTim6ZBWw66rzx_gSvWc9E45EZx2_gw@mail.gmail.com>	<BANLkTinxG6FtOqa8KzmvgTT1EFfM-6prow@mail.gmail.com>	<BANLkTinsnqGSVTz=XPhCfX95mfeJ_pkhCg@mail.gmail.com>	<BANLkTi=nwij4sfkKnNdM_NP9w2CArK6NHQ@mail.gmail.com>	<BANLkTikghRix9VbpHDx+rnCRtnjdjeshmg@mail.gmail.com>	<718216446.20110408143441@cypressintegrated.com>	<4DA0E71C.9030008@gmail.com>	<BANLkTi=jJTO3qgjN8=3DCKAV88pnvycVsA@mail.gmail.com>	<op.vtp8l9jnr8a5bd@localhost>	<4DA63ED8.4080402@yahoo.com.au>	<op.vtw5fnjar8a5bd@localhost>	<BANLkTi=jFJpqEX+8_yiCZbKVkYc1+EhnSw@mail.gmail.com>	<BANLkTinPUnzXpfj8AVeaUBi1YSgveCzrPA@mail.gmail.com>	<4DA6F2BC.10706@yahoo.com.au>	<BANLkTi=4SD2fzwMc5uLquBkHeBmxDRC0DA@mail.gmail.com>	<4DA6FB03.9040404@yahoo.com.au>	<BANLkTimiH2vYWEY8JAf0P_GD81AqGmStDQ@mail.gmail.com> <BANLkTinRpxgoYBc=H1uBqwLiCOmKA3zD+A@mail.gmail.com> <4DAF8105.5060105@gmail.com>
In-Reply-To: <4DAF8105.5060105@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Implicit isset/isempty check on short-ternary operator
From: mail_ben_schmidt@yahoo.com.au (Ben Schmidt)

> What does coalesce() do?
> If I'm guessing correctly, would  proposal #2 that Rune Kaagaard put up
> solve that for you?
> https://gist.github.com/909711

Rune's proposal #2, extending func_get_arg(), is impossible to
implement/would not work.

His proposal #3, which is more like coalesce(), suffers from the
drawbacks/problems of coalesce() which I discussed in a recent post
(though you can see Rune has some workarounds/hacks to deal with some of
the problems).

IMHO, his proposal #1 is the only real contender. However, I believe it
conflates two problems which others do not want conflated. He briefly
dismisses the [?] syntax, because it addresses what he sees as a
different problem. However, that different problem is really part of his
problem. My contention is that the two parts of his problem are better
solved independently (notice-suppression separately to finding an
isset/!empty value), and furthermore that one of the two versions of his
problem is already partially solved and should be reused, not reinvented
(existing ternary operator for a !empty check).

Ben.