On Mon, 23 Oct 2006, Marcus Boerger wrote:
> after recent discussions (over the last three months)I finally made up my
> mind over E_STRICT, deprecation warnings and OOP messages/rules. My idea
> proposal is to do the following:
>
> - Add a new severity E_DEPRECATED
+1
> - severities are used as follows:
> . E_DEPRECATED: Some language featre that is likely to go away. Eearlierst
> removal would be two minor versions or one major version later. That is
> something that gets deprecated in 5.2 can be removed in 5.4.0 or 6.0.0.
> However both marking it as deprecated as well as removing it would
> require a consensus on the list.
+1
> . E_STRICT any rule that reflects common strict standards, like OOP theory
> that is considered harmless if not followed. For example the combination
> 'abstract static' makes no sense in said theory but doesn't put our zend
> engine in an unstable state.
+1, but then we should also expand this to include:
- setting object variables without declaring them
- auto-creating objects of stdclass on the fly
- and other things that you *should* (not) do
These can be added later ofcourse, doesn't have to be directly in
5.2.0, however that would probably be better.
> . E_NOTICE or E_WARNING are used for input validations (e.g. domain errors).
+1, but I think we need to specify when exactly to use E_NOTICE,
E_WARNING, E_RECOVERABLE_ERROR and E_ERROR as well.
> - We drop the current standard INI files and provide two new, namely
> . php-develop.ini for developing (E_ALL|E_STRICT|E_DEPRECATED)
> . php-production.ini for production (~(E_DEPRECATED|E_NOTICE|E_WARNING))
> . E_ALL does not contain E_STRICT or E_DEPRECATED
-1, We should include E_DEPRECATED in E_ALL.
> - We delay 5.2.0 and revisit all errors and change them according to the
> new model. We also put any change into the upgrading file.
+1
regards,
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
