Re: [RFC] Allow non-variable arguments to empty() and isset()

From: Date: Fri, 04 May 2012 18:48:08 +0000
Subject: Re: [RFC] Allow non-variable arguments to empty() and isset()
References: 1 2 3 4 5 6  Groups: php.internals 
Request: Send a blank email to internals+get-60447@lists.php.net to get a copy of this message
On Wed, May 2, 2012 4:43 am, Pierre Joye wrote: >>> empty() on the other hand, tests if something is empty, and only if >>> it >>> is empty. The result of an expression can be empty. >>> >> >> an expression can also have a value of null. > > And NULL is empty. No issue here. Expressions can also return "", 0, 0.0, "0", array() You really think those should all be empty? Or you want different behavior for expressions vs variables. I'm assuming virtually everybody would agree THAT is unacceptable... Or are the rules for what is or isn't empty going to also change. Again. -- brain cancer update: http://richardlynch.blogspot.com/search/label/brain%20tumor Donate: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE

« previous php.internals (#60447) next »