Error messages for wrong coding
| From: | Felipe Pena | Date: | Tue, 19 Feb 2008 03:21:20 +0000 |
| Subject: | Error messages for wrong coding | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-35575@lists.php.net to get a copy of this message | ||
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:
Actual result:
$a = 1234;
$a[0]; // Not shows error
Proposed:
- Shows error message (Fatal error, as happens with objects) for
integer and float variables.
http://felipe.ath.cx/diff/bug39915.diff
---
Bug #42852 - Inconsistent message when creating default object from
empty value:
Actual result:
$obj1->p = 1; // Shows 'Strict Standards ...'
$obj2->p[] = 1; // Not shows
$a = 1;
$obj3->p = &$a; // Not shows
Proposed:
- 'Strict Standards' for all cases.
http://felipe.ath.cx/diff/bug42852.diff
--
Regards,
Felipe Pena.