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

From: Date: Sat, 10 Jul 2004 09:43: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 17  Groups: php.internals 
Request: Send a blank email to internals+get-11065@lists.php.net to get a copy of this message
Hello Christian, Saturday, July 10, 2004, 10:35:38 AM, you wrote: > Andi Gutmans wrote: >> 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 > Thanks for these words of wisdom, Andi. > Dismissing a solution because the implementation seems hard at first is > not what we should do here. Well normally we just commit don't we? Also believe me or not i worked out my patch very hard and tried other things to. But feel free to ignore my efforts. >> At 01:54 AM 7/10/2004 +0200, Marcus Boerger wrote: >>> coalesce would be: >>> "coalesce" "(" <var> ( "," <var> )* [ >>> "," <expr> ] ")" > Actually I'd prefer > "coalesce" "(" <expr> ( "," <expr> )* > ")" > with either the whole expression evaluation silenced or only in the case > where <expr> is a <var>. > I'll have a go at it as soon as I find time. Anyway i appreciate if you try to find a solution! As a hint <var> and <expr> are two very different things. That's why i chose the syntax to be "ifsetor(<var>,<expr>)". And i am quite sure we cannot change <var> to <expr> -- Best regards, Marcus mailto:helly@php.net

« previous php.internals (#11065) next »