At 03:02 PM 5/30/2006, Marcus Boerger wrote:
whatever the patch looks like, it is a change from 5.0.0's E_STRICT
to a E_COMPILE_ERROR and actually fixes another problem. This raises
an interesting question. How long must we wait until we can follow the
E_STRICT idea and change a specific E_STRICT into a fatal error. Must
it be until eternity?
E_STRICT doesn't mean that those warnings will become errors down the road. It just enforces best practices, and some might deprecate and some might not...
Now that's why I suggested E_DEVEL for 'advisory' issues. The problem is that E_STRICT, according to the manual and most of the dev team, is only there for 'real' deprecation issues.
- Steph
Andi