Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51916
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain yahoo.com.au from 98.139.52.220 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:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
  b=aecFM6fiS0Rd6s9fM745fIIdfhnxVSbPzIJbj7gcByFLyOVuNCvaWZkFqPO6o3wNlXuVaL3PngfybuPYoCF8y9yvWbEhDSLlQMKvX1dl6Rg2dCGJW6HkHR+UJxBGYW3cKaSmBt01bZ4y+dLSMPVXAfDo63DjhwyNv5P3QqQYggk=  ;
Message-ID: <4DA98D34.1020909@yahoo.com.au>
Date: Sat, 16 Apr 2011 22:36:04 +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: Adam Richardson <simpleshot@gmail.com>
CC: PHP Development <internals@lists.php.net>
References: <AANLkTiknomAsTrsZ140rWs6CwxJP3UYGUokQbERhDiRp@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>	<BANLkTinzDxa8gH08qBggrLzziAVb_oksng@mail.gmail.com>	<4DA8E6D9.5080107@yahoo.com.au> <BANLkTi=rz3pj2DuXytWxfBA2etdc1YAo-A@mail.gmail.com>
In-Reply-To: <BANLkTi=rz3pj2DuXytWxfBA2etdc1YAo-A@mail.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)

> I believe describing nullness checking as a "main" issue is a rather
> strong assessment.

I don't think so, obviously. :-)

> $var = (isset($arr['key'])) ? $arr['key'] : 'empty';

Nullness checking is half of what that code does, isn't it? Otherwise it
would be (isset($arr['key']) && $arr['key']), right?

> Additionally, it might not be as succinct as you prefer, but surely
>
> $var = $arr['key'] ?? : 'empty';
>
> is a significant improvement over the current means and does in fact remove
> redundant code.

But it's not equivalent to your code snippet above, is it?

My vote's still with the line of discussion Hannes and I were on, of
separate 'careful array index lookup' and 'default-when-null'
operator(s). Partly because I think that approach can help everyone,
whereas the checked ternary operator really doesn't help me much at all.
Not sure if that's selfish or not. :-)

I'll try to stay a bit quieter for a bit, if I can manage it.... I've
said a lot today.

Returning due respect,

Ben.