Hi,
This seems like a trivial change from the implementation side, so I am
not worried about changing this for the "better" even after RC4 (given
proper documentation.
So here are the choices I see:
1) stay as is .. aka defaults to on while not emiting an E_DEPRECATED,
do emit E_DEPRECATED when using the setter
2) as per Zeev, leave the default as is and change things when using
the setter as follows: "emit E_DEPRECATED in case of true and nothing
in case of false; For 6 - emit an error for true and nothing for
false." (so he is also suggesting to revert the removal of the setter
in PHP6)
3) stay as is .. aka defaults to on while not emiting an E_DEPRECATED,
but do not emit E_DEPRECATED when using the setter to disable
4) change the default to off, for the rest stay as is
A few notes:
First up we are late in the RC stage. Also E_DEPRECATED is a "checker
tool" you enable temporarily during development. I expect most people
to use a php.ini supplied by whatever distro they are using or simply
update their current php.ini, in which case they are most likely
setting a value for this setting explicitly, which should cause and
E_DEPRECATED if enabling this feature. I am also not sure which if the
other settings that we are removing in PHP6 are also on by default,
but obviously if we change something here, we are opening pandora's
box to those as well:
- define_syslog_variables
- register_globals
- register_long_arrays
- safe_mode
Please keep things as concise as possible when you reply.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
