Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10988
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 8 Jul 2004 20:50:01 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <71425903.20040708205001@marcus-boerger.de>
To: Marc Richards <contact_marcos@yahoo.es>
Cc: internals@lists.php.net
In-Reply-To: <20040708140845.13476.qmail@pb1.pair.com>
References: <20040708002654.7442.qmail@pb1.pair.com>
 <1093095066.20040708032739@marcus-boerger.de>
 <20040708140845.13476.qmail@pb1.pair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] what happened to that new isset() like language construct
From: helly@php.net (Marcus Boerger)

Hello Marc,

Thursday, July 8, 2004, 4:07:54 PM, you wrote:

> Marcus Boerger wrote:
>> Hello Marc,
>> 
>> it somply was far too lat3e in relase process. That's wy we ae all agreed
>> to delay that until 5.1. Also we were very unsure about the name of such
>> an operator....if you can collect all the ideas or can come up with ther
>> perfect one!?!
>> 

> Well I'm partial to ?: and there seemed to be some support for it, but 
> there also seemed to be a non-trivial (though not necessarily difficult) 
> amount of work to get it to work right.

?: would require a default value. ifsetor() allows to assume NULL hence
the latter is more powerfull. Hence id like to see a new keyword.

Best regards,
 Marcus                            mailto:helly@php.net