[prev in list] [next in list] [prev in thread] [next in thread]
List: php-doc-cvs
Subject: [DOC-CVS] =?utf-8?q?svn:_/phpdoc/en/trunk/reference/errorfunc/_ini.xml?=
From: Sherif_Ramadan <googleguy () php ! net>
Date: 2012-07-28 4:02:26
Message-ID: svn-googleguy-1343448146-326841-67921519 () svn ! php ! net
[Download RAW message or body]
googleguy Sat, 28 Jul 2012 04:02:26 +0000
Revision: http://svn.php.net/viewvc?view=revision&revision=326841
Log:
Fixed out-dated E_STRICT information in error_reporting doc.
Changed paths:
U phpdoc/en/trunk/reference/errorfunc/ini.xml
Modified: phpdoc/en/trunk/reference/errorfunc/ini.xml
===================================================================
--- phpdoc/en/trunk/reference/errorfunc/ini.xml 2012-07-28 03:37:31 UTC (rev 326840)
+++ phpdoc/en/trunk/reference/errorfunc/ini.xml 2012-07-28 04:02:26 UTC (rev 326841)
@@ -167,9 +167,13 @@
Prior to PHP 5.4.0 <constant>E_STRICT</constant> was not included within
<constant>E_ALL</constant>, so you would have to explicitly enable this kind of
error level in PHP < 5.4.0. Enabling <constant>E_STRICT</constant> during development
- has some benefits. STRICT messages will help you to use the latest and
- greatest suggested method of coding, for example warn you about using
- deprecated functions.
+ has some benefits. STRICT messages provide suggestions that can help
+ ensure the best interoperability and forward compatibility of your code.
+ These messages may include things such as calling non-static methods
+ statically, defining properties in a compatible class definition while
+ defined in a used trait, and prior to PHP 5.3 some deprecated features
+ would issue <constant>E_STRICT</constant> errors such as assigning
+ objects by reference upon instantiation.
</para>
</note>
<note>
--
PHP Documentation Commits Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic