Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:11056
Return-Path: <robert@interjinn.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 40627 invoked by uid 1010); 10 Jul 2004 01:12:13 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 40602 invoked from network); 10 Jul 2004 01:12:12 -0000
Received: from unknown (HELO blobule.suds) (66.11.170.154)
  by pb1.pair.com with SMTP; 10 Jul 2004 01:12:12 -0000
Received: by blobule.suds (Postfix, from userid 501)
	id 52E362F727; Fri,  9 Jul 2004 21:12:10 -0400 (EDT)
To: Marcus Boerger <helly@php.net>
Cc: Daniel Crookston <daniel@hyperion-data.net>,
	internals@lists.php.net
In-Reply-To: <1698304637.20040710015450@marcus-boerger.de>
References: <5.1.0.14.0.20040707203931.02fa6200@mail.ionzoft.com>
	<40ED64A0.7050305@cschneid.com> <20040708151952.92187.qmail@pb1.pair.com>
	<Pine.LNX.4.58.0407080929200.2055@thinkpad.lerdorf.com>
	<20040708215205.23281.qmail@pb1.pair.com>
	<Pine.LNX.4.58.0407081454280.2055@thinkpad.lerdorf.com>
	<20040708222005.4329.qmail@pb1.pair.com>
	<Pine.LNX.4.58.0407081523470.2055@thinkpad.lerdorf.com>
	<20040708233326.73283.qmail@pb1.pair.com>
	<Pine.LNX.4.58.0407081937310.21867@miranda.org>
	<20040708235341.42767.qmail@pb1.pair.com>
	<007201c4655d$283125d0$6601a8c0@calhoun>
	<1098364181.20040709084904@marcus-boerger.de>
	<1089386722.26206.2.camel@blobule.suds> 
	<1698304637.20040710015450@marcus-boerger.de>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8-3mdk 
Date: 09 Jul 2004 21:12:09 -0400
Message-ID: <1089421929.7560.2.camel@blobule.suds>
Mime-Version: 1.0
Subject: Re: [PHP-DEV] what happened to that new isset() like language
From: robert@interjinn.com (Robert Cummings)

On Fri, 2004-07-09 at 19:54, Marcus Boerger wrote:
> Hello Robert,
> 
>  coalesce would be:
> 
>  "coalesce" "(" <var> ( "," <var> )* [ "," <expr> ] ")"
> 
> and would also require heay engine patching. I am speaking of a
> really major change here, i already looked into what it would
> need month's ago. Since the operator i proposed is different from
> the coalesce functionality many sql developers know i see that as
> a definitive no. But again if you give the engine a try :-)

Sorry, I thought I was following the thread quite thoroughly, but I
missed the part until earlier today where the functionality would
involve shortcutting expression evaluation if a non-null or set value
was found. Obviously (I think -- correct me if I'm wrong) without the
shortcutting feature, implementation would be simplistic.

Cheers,
Rob.
-- 
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com |
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting  |
| a powerful, scalable system for accessing system services  |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for       |
| creating re-usable components quickly and easily.          |
`------------------------------------------------------------'