AW: AW: [PHP] PHP is Zero
| From: | BUSCHKE Daniel | Date: | Thu, 13 Jun 2013 11:49:31 +0000 |
| Subject: | AW: AW: [PHP] PHP is Zero | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-321387@lists.php.net to get a copy of this message | ||
To be more technical:
If intval('8315e839da08e2a7afe6dd12ec58245d') would return NULL instead of 8315 then PHP
would be still weak-typed and the developer could know that the conversion failed. Good idea? Of
course NULL should be transparent in operations like +. So 0 + NULL should be still 0.
Regards
Daniel
-----Ursprüngliche Nachricht-----
Von: BUSCHKE Daniel
Gesendet: Donnerstag, 13. Juni 2013 13:28
An: 'Pete Ford'; php-general@lists.php.net
Betreff: AW: AW: [PHP] PHP is Zero
Hi,
> It gives up when it finds a non-numeric character (as the documentation would tell you)
Why is PHP doing that? I know it works as designed and I know it is documented like this but that
does not mean that it is a good feature, does it? So lets talk about the question: Is that behaviour
awaited by PHP software developers? Is that really the way PHP should work here? May we should
change that?!
BTW: I talked to some collegues and friends since my first post. They all guessed that
"'PHP' == 0" is false within a few seconds. I think the weak-typed-PHP is a
little to weak at this point.
Regards
Daniel