Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51828
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.218.42 cause and error)
Message-ID: <4D9E34C4.5000406@lerdorf.com>
Date: Thu, 07 Apr 2011 18:03:48 -0400
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Matthew Weier O'Phinney <weierophinney@php.net>
CC: internals@lists.php.net
References: <AANLkTiknomAsTrsZ140rWs6CwxJP3UYGUokQbERhDiRp@mail.gmail.com> <4D950434.3060704@yahoo.com.au> <BANLkTinzb5xiD8j7ZXB+cT4EBZY3DF6BYQ@mail.gmail.com> <4D9E0543.1080600@lerdorf.com> <69.82.36433.EC33E9D4@pb1.pair.com>
In-Reply-To: <69.82.36433.EC33E9D4@pb1.pair.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: rasmus@lerdorf.com (Rasmus Lerdorf)

On 4/7/11 5:59 PM, Matthew Weier O'Phinney wrote:
> It may change the semantics as they stand, but I'd argue that the
> _expectation_ from the shorthand ternary is to shorten code that
> currently uses isset(). As it is, I have almost no use for it at this
> point, as I end up needing to do:
>
>      $value = isset($a[$key]) ? $a[$key] : 'Not set';
>
> which is exactly the situation I had before it was introduced.

Not sure why you would have that expectation. The long ternary doesn't 
do that, and there is nothing about the short ternary that changes that. 
There was talk of a new ifsetor type of operator to have those semantics 
but never any talk of changing existing semantics.

-Rasmus