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

I don't think it's a matter of giving the engine a try. I think we first need to make a decision what the best way to go is and then we can discuss implementation if/what is possible. Once 5.0.0 is out I'm going to have more time look into this. At 01:54 AM 7/10/2004 +0200, 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 :-) mfG marcus Friday, July 9, 2004, 5:25:22 PM, you wrote: On Fri, 2004-07-09 at 02:49, Marcus Boerger wrote:

Hello Daniel, Friday, July 9, 2004, 4:33:42 AM, you wrote:

Why not just call it the issetor, or the setor operator?

That's the point here. How shall we call the new operator.

I'm +1 on the "coalesce" name since I even think having the funciton support multiple parameters and return the first set/not null value would provide more utility to developers. Cheers, Rob. -- Best regards,

 Marcus                            mailto:helly@php.net

-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php