#define E_ALL (E_ERROR | E_WARNING | E_PARSE | E_NOTICE | E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR | E_COMPILE_WARNING | E_USER_ERROR | E_USER_WARNING | E_USER_NOTICE)
I guess either slotting E_STRICT in the and defining E_ALL_PHP5 or (E_ALL_PHP4 and redefining E_ALL).. probably worth sticking in a few for future use... so the same problem doesnt occur again..???
E_UNUSED_1
E_UNUSED_2
E_UNUSED_3
E_UNUSED_4
E_UNUSED_5
Regards Alan
Lukas Smith wrote:
From: Andi Gutmans [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 30, 2003 12:10 AM
The strict was introduced so that we can add warnings about practices we
recommend and deprecated behavior.
I think "var" belongs there.
We could remove E_STRICT from E_ALL (although that'd be a bit hacky) and
save ppl the trouble of seeing these warnings.
Then again, we could remove the warning about var but I'm not sure I'd
want
to do that.
Well I would make E_ALL a subset of E_STRICT. This would be the cleanest for BC. Of course it might be confusing since "ALL" implies everything ..
Regards, Lukas
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
