Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10979
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20040708140845.13476.qmail@pb1.pair.com>
To: internals@lists.php.net
Date: Thu, 08 Jul 2004 10:07:54 -0400
User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626)
MIME-Version: 1.0
References: <20040708002654.7442.qmail@pb1.pair.com> <1093095066.20040708032739@marcus-boerger.de>
In-Reply-To: <1093095066.20040708032739@marcus-boerger.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] what happened to that new isset() like language construct
From: contact_marcos@yahoo.es (Marc Richards)



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.

ifsetor() is obviously less concise, but also the name at first glance 
is a little non-obvious/confusing. I suppose isset() suffers from the 
same problem, and people will eventuall get used to it.

If the technical problems can be overcome, I'm all for ?: otherwise 
ifsetor() seemed like the best suggestion so far.  I am far less 
qualified to come up with an alternative than the more experienced 
PHP'ers out there.


Marc