PHPStrictStandards error _ PHP Tutorial

PHPStrictStandards errors. The day before yesterday, I accidentally modified the php. ini settings for error output. when I tested a CakePHP project today, I found several more error messages. although they are not fatal, they cannot be ignored. The day before yesterday, I accidentally modified the php. ini settings for error output. when I tested a CakePHP project today, I found several more error messages. although they are not fatal, they cannot be ignored.

The error description is as follows: www.2cto.com

Strict Standards: Redefining already defined constructor for class Object in D: \ www \ hosts \ cake \ ucake-libs \ cake \ libs \ object. php on line 69

Strict Standards: Assigning the return value of new by reference is deprecated in D: \ www \ hosts \ cake \ ucake-libs \ cake \ libs \ object. php on line 94

Strict Standards: Assigning the return value of new by reference is deprecated in D: \ www \ hosts \ cake \ ucake-libs \ cake \ libs \ security. php on line 48

Strict Standards: Assigning the return value of new by reference is deprecated in D: \ www \ hosts \ cake \ ucake-libs \ cake \ libs \ inflector. php on line 65

Strict Standards: Assigning the return value of new by reference is deprecated in D: \ www \ hosts \ cake \ ucake-libs \ cake \ libs \ configure. php on line 89

Strict Standards: Non-static method Configure: getInstance () shocould not be called statically in D: \ www \ hosts \ cake \ ucake-libs \ cake \ bootstrap. php on line 43

Strict Standards: Non-static method Configure: write () shocould not be called statically in D: \ www \ hosts \ cake \ ucake-libs \ cake \ bootstrap. php on line 82

Strict Standards: Non-static method Configure: getInstance () shocould not be called statically in D: \ www \ hosts \ cake \ ucake-libs \ cake \ libs \ configure. php on line 108

I scanned a few eyes and found that it was basically a CakePHP framework error. when I searched for related error information in Google, I found that other frameworks also had such a common problem...

I had to carefully read the explanation of the error. what I understand is that the program did not write the warning according to the strictly prescribed PHP mode. After thinking of this, I tested several small programs I wrote earlier, and some of them will also see this error. It seems that you have to pay attention to your coding specifications in the future, and you cannot simply pursue functions...

As the current project needs to be debugged, the php. ini error output is redefined as error_reporting = E_ALL. Remove E_STRICT and restart Apache... Everything is always...

From joy's

....