2008/2/19, Cristian Rodriguez <[EMAIL PROTECTED]>:
>
> There is a similar case with unset() an offset of booleans and integers.
>
> $foo = true:
> /* should throw a fatal error, like it does when trying to unset string
> offsets.
> actually $foo remains unchanged after unset() (!!)
> unset($foo[0]
2008/2/19, Felipe Pena <[EMAIL PROTECTED]>:
> Em Ter, 2008-02-19 às 01:25 -0300, Cristian Rodriguez escreveu:
> > you need to handle offset of booleans too..
>
> Oops! Thanks.
There is a similar case with unset() an offset of booleans and integers.
http://www.cristianrodriguez.net
Em Ter, 2008-02-19 às 12:28 +0100, Marcus Boerger escreveu:
> This patch results in two error message for type long, one complaining about
> long, one about double. You can use function zend_get_type_by_const() to
> avoid this. Also make sure that we see the new style message for type bool
> and a
Hello Felipe,
Tuesday, February 19, 2008, 4:21:20 AM, you wrote:
> Hi.
> Looking on "Feature/Change Request", i have seen curious things, and i
> think that them should issue any error message. See above.
> ---
> Bug #39915 - Trying to access the index of an integer should throw a
> warning:
>
2008/2/19, Cristian Rodriguez <[EMAIL PROTECTED]>:
> 2008/2/19, Felipe Pena <[EMAIL PROTECTED]>:
>
> >
> > Proposed:
> > - Shows error message (Fatal error, as happens with objects) for
> > integer and float variables.
> >http://felipe.ath.cx/diff/bug39915.diff
>
> +1 , fatal error for consist
2008/2/19, Felipe Pena <[EMAIL PROTECTED]>:
>
> Proposed:
> - Shows error message (Fatal error, as happens with objects) for
> integer and float variables.
>http://felipe.ath.cx/diff/bug39915.diff
+1 , fatal error for consistency.
>
> Proposed:
> - 'Strict Standards' for all cases.
>ht
