On 10/27/05, Derick Rethans <[EMAIL PROTECTED]> wrote:
>
> On Wed, 26 Oct 2005, Ilia Alshanetsky wrote:
>
> > IMHO this is a bad idea, if you really wanted to support NULL in a
> > particular case you, as a developer could do:
> > php -r '$n=NULL; foreach((array)$n as $v);'
> >
> > Making NULL usage transparent where array is expects will lead to
> > difficult to debug code.
> >
> > -1 for removing the warning.
>
> Yes, I agree, we should not remove this warning.
>
> Derick
+1 on *not* removing the warning. I can't see any reson why it should be
removed.
php -r '$foo = array(2, 3, 4); echo substr("foobar", $foo). "\n";'
currently prints "oobar". Would like to see, as Jani suggested, E_STRICT
notice thrown when wrong data type is passed to a function/language
construct.
- Hannes
