Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26465
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain adaniels.nl from 82.94.235.198 cause and error)
Message-ID: <45547DF7.8080805@adaniels.nl>
Date: Fri, 10 Nov 2006 14:26:15 +0100
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: internals@lists.php.net
Content-Type: multipart/alternative;
 boundary="------------080507030201080008020802"
Subject: Yet another feature request
From: info@adaniels.nl (Arnold Daniels)

--------------080507030201080008020802
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I see this is the time to do language feature request. So let me add 
another. I very often use something like:
/$a = isset($x['abc']) ? //$x['abc'] : null;
/This is to prevent an E_NOTICE from being thrown.

This subject is already discussed many times, which led to a suggestion 
for PHP6 
(http://www.php.net/~derick/meeting-notes.html#ifsetor-as-replacement-for-foo-isset-foo-foo-something-else)
/$foo = $_GET['foo'] ?: 42;/
This still throws an E_NOTICE when the first parameter is not set. Also 
$foo will be set to 42 if the input variable is 0. The conclusion is 
that this feature is useless for the presented situation.

I would like something similar to isset: ifsetor($var, [$default = null]);
/$a = ifsetor($x['abc']);
//$foo = ifsetor($_GET['foo'], 42);
/
I believe adding this feature will remove the biggest con people have on 
working with E_NOTICE enabled. I'm sorry if I reopen an already closed 
subject.

Best regards,
Arnold

--------------080507030201080008020802--