#25243 [Bgs->WFx]: casting to int behavior weird

ID: 25243 Updated by: derick@php.net Reported By: elite_eagle67 at hotmail dot com -Status: Bogus +Status: Wont fix Bug Type: Feature/Change Request Operating System: windoze PHP Version: Irrelevant New Comment: We will not break other people's scripts. Previous Comments: ------------------------------------------------------------------------ [2003-08-26 17:43:21] elite_eagle67 at hotmail dot com Ok then I move this to a feature request. Im asking then that if the behavior of array to int, object to int, etc is predictable and in the manner I described IE any non integer value will be converted to 0 when casted to int as you think it would be. Thanks. ------------------------------------------------------------------------ [2003-08-25 23:27:20] sniper@php.net RTFM: http://www.php.net/manual/en/language.types.integer.php#language.types.integer.casting ------------------------------------------------------------------------ [2003-08-25 23:21:18] elite_eagle67 at hotmail dot com Description: ------------ Do (int)$var where $var is an array that has some kind of value stored, and the return value will be 1, not 0. Now this obviously doesn't make sense as you cast to (int) so you can see if a variable has a valid INTEGER variable, NOT if it is the integer equivilent of a * boolean * value. Ofcourse, an empty array in this example will return 0, as would be expected behavior for a BOOLEAN cast, not integer howerever... I'm unaware how (string) cast deals with this, possibly similiar but if so, then just apply this bug report to that ;) Reproduce code: --------------- $array = array( 'yay' => 'boo!' ); if((int)$array) { echo (int)$array; } else { echo (int)$array; } Expected result: ---------------- 0 Actual result: -------------- 1 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=25243&edit=1