ID: 31004 Updated by: [EMAIL PROTECTED] Reported By: levi at alliancesoftware dot com dot au -Status: Open +Status: Bogus Bug Type: Documentation problem PHP Version: 5CVS-2004-12-07 (dev) New Comment:
Purpose of E_STRICT is stated at http://php.net/errorfunc#ini.error-reporting : "STRICT messages will help you to use the latest and greatest suggested method of coding, for example warn you about using deprecated functions." There's nothing about issuing errors when working with undefined member variables. Previous Comments: ------------------------------------------------------------------------ [2005-01-12 01:03:30] [EMAIL PROTECTED] It was never supposed to do so. Reclassifying as documentation problem, as I doubt it will change ever. ------------------------------------------------------------------------ [2004-12-07 08:30:06] levi at alliancesoftware dot com dot au Description: ------------ If you use strict error reporting, and set an object member variable that does not exist no error is triggered. The point of strict error reporting is supposed to be to catch programming errors and ensure maximum future compatability -- shouldn't it report exactly this type of situation? Note: Verified only with 5.0.3RC1 (The CVS copy was the closest in the list) Reproduce code: --------------- <? error_reporting(E_ALL | E_STRICT); class Object { var $property; function __construct() { $this->proper = 1; // missing the last two letters! } } $x = new Object(); ?> Expected result: ---------------- Should trigger an error Actual result: -------------- - ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=31004&edit=1
