E_STRICT

Created by: Lester Caine, Last modification: 5 January 2014

As yet I've not found a complete explination of just what is affected that creates the E_STRICT warning. There is certainly not a good explination of where it even came from in the PHP manua, and the current site search seems to miss quite a large section of the website. E_STRICT was introduced with PHP5 as a means of flagging code which does not comply with the new style model, but just what that style model is does not get documented?

PHP4 based code will have a number of elements that create E_STRICT errors, and enabling the E_STRICT level of error reporting quite often results in white screen errors when trying to run legacy sites. It is hoped that we can build up a set of guidelines which will remove the major problems and then at least allow the in-line debugging to work, but often the first you know of a problem is when an ISP updates their PHP version, and sites stop working. While it may make sense that simply disabling E_STRICT again in PHP5.4 installations will allow sites to continue working, this can not be sustained where the default is for that flag to be enabled. The high volume of sites remaining on PHP5.2 and 5.3 will need a concerted effort to rewrite to be E_STRICT compliant.

TODO

  1. Produce a list of style fixes that need to be applied to tidy up to remove E_STRICT errors.
  2. Produce a list of style fixes that need to be applied to tidy up to remove E_STRICT warnings.
  3. Produce a clean style document for PHP5 as a base to address code re-writes.