Re: Inconsistency of empty() and isset() ?

We had a huge thread about this a while back (1-2 years) where this was discussed in great depth. The agreement was that for isset() it's very straight forward and usefull and that the semantics with empty() would be confusing and problematic, and therefore, the decision was to just support this for isset(). For the full reasoning I suggest to search the archives. Shouldn't take too long to find. Andi At 04:24 PM 4/16/2006, Richard Lynch wrote:

On Sun, April 16, 2006 4:40 pm, Derick Rethans wrote: On Sat, 15 Apr 2006 itrebal@gmail.com wrote: There is a thought about it, and that is that we could not decide whether it should be an AND or an OR test between the different parameters. I'm curious to know whoulda thunk it would be OR, and why?... I mean, the most common usage I've seen, bar far, is for form input validation of a zillion inputs. I've never quite grokked why others think empty is "better" than isset for that, and don't really want to even get into that thread (again) here, but I am interested to know when you'd have a whole BUNCH of args to test with empty and would want OR on a regular frequent basis. -- Like Music? http://l-i-e.com/artists.htm -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php