Re: [PHP-DEV] $string != $array should throw a warning! From: Andi Gutmans (andi <email protected>)
Date: 12/28/99

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? 

-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
For additional commands, e-mail: php-dev-help <email protected>
To contact the list administrators, e-mail: php-list-admin <email protected>