> Maybe we should move this to an E_STRICT? E_WARNING is more consistent with > existing warnings but I wouldn't want to be over strict, especially when > making this change a couple of weeks before release. > We could escalate the warning for 5.1 if we feel we need to do so. > While I have a....layer of skepticism about the approach Aidan described, I can see the wisdom in easing into error throwing. Let's go ahed and start with E_STRICT and discuss an elevation to either E_NOTICE (similar to implicitly casting unknown constants to strings), or E_WARNING.
-Sara -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
