Re: what happened to that new isset() like language

From: Date: Sat, 10 Jul 2004 09:37:15 +0000
Subject: Re: what happened to that new isset() like language
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16  Groups: php.internals 
Request: Send a blank email to internals+get-11064@lists.php.net to get a copy of this message
Hello Robert, Saturday, July 10, 2004, 3:12:09 AM, you wrote: > 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. The problem here is computing the jump addresses and targets needed. Best regards, Marcus mailto:helly@php.net

« previous php.internals (#11064) next »