On Thu, 13 Jul 2006, Lukas Smith wrote: > Lukas Smith wrote: > > Ok I see 2 options: > > 1) > > Obviously one solution would be to disallow making anything an E_STRICT > > notice that is not available since the first release of the given major > > version. > > Pierre and Anthony seem to favor this solution.
E_STRICT is meant as a tool for us (php developers) to signal possible bad usage of the language and/or possible BC breaks in the future. Therefore it's perfectly valid to require the update of a package in order to be E_STRICT compatible with a later PHP version. I doubt that (for e_strict) there won't be a solution that works on older PHP versions. It is *that* that we need to make sure doesn't happen then and we're in the clear. Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
