Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61394
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: fail (pb1.pair.com: domain rafaeldohms.com.br does not designate 209.85.220.170 as permitted sender)
MIME-Version: 1.0
Date: Wed, 18 Jul 2012 16:15:44 +0200
Message-ID: <CAOhuFvYD8FQw=xbK3hFqi4GYkOvCNzWjuhk2fqwBjKG9n2kuuQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec54eeffc7eea5304c51b4cb6
Subject: Implicit isset in ternary operator
From: listas@rafaeldohms.com.br (Rafael Dohms)

--bcaec54eeffc7eea5304c51b4cb6
Content-Type: text/plain; charset=ISO-8859-1

Hey Everyone,

With the syntax improvements for 5.4 and some of the de-referencing work,
code looks so much sleeker then before, but there is still one use case
that really bugs me.

Given this code:

$width = (isset($config['width']))? $config['width'] : 300;

The code is pretty straight forward, if width is set in the array, use it
otherwise use 300.

This code would look much better if it could make use of the ternary
operator

$width = $config['width'] ?: 300;

The only reason for this to not work is: it throws a notice if the array
key is not there (which is the case we are covering anyway)

This is basically because the ternary operator does not do a internal
implicit isset, only an empty.

Does this seem like a possible improvement we can work on? Anyone
interested in championing the change?

-- 
Rafael Dohms
PHP Evangelist and Community Leader
http://www.rafaeldohms.com.br
http://www.phpsp.org.br

--bcaec54eeffc7eea5304c51b4cb6--