Re: $string != $array should throw a warning!

From: Date: Tue, 28 Dec 1999 20:16:11 +0000
Subject: Re: $string != $array should throw a warning!
References: 1  Groups: php.dev php.version4 
Request: Send a blank email to php-dev+get-14105@lists.php.net to get a copy of this message
On Tue, 28 Dec 1999, Thies C. Arntzen wrote: > > On Tue, 28 Dec 1999, Andi Gutmans wrote: > > > Yeah they should be bool in my opinion too. How about entering it in > > bugs.php.net/version4 so that we remember to fix it. > > andi, > the fix is too easy to put it in bugdb, question is how do we want to fix > it: > > a) spit a warning in compare-function & still return var_reset()? We should be returning false (bool(0)) in these functions. We'll have to hold a vote if we should spit out a warning or not. I think we should because it's a coding error. > b) decide if array > string or vice versa No we don't want this kind of unintuitive stuff in PHP. It is undefined as far as I'm concerned. > just have a quick look at compare_function and you'll see what i mean. > > as the current behaviour is undefined i'd go for b) and declare "Array > > string" (that was choosen by random), 'cause i don't like the idea of an > basic operator to spit a warning. > > comments?

« previous php.dev (#14105) next »