Hello Timm, Friday, February 27, 2004, 7:39:26 PM, you wrote:
> On Fri, 2004-02-27 at 14:39, Stig S. Bakken wrote: >> On Fri, 2004-02-27 at 14:13, Derick Rethans wrote: > [...] >> What is worse is that many PHP 4 APIs need to be completely redesigned >> for PHP 5, not only the guts of the class. >> >> IMHO method overloading the the only clean way out of this. > Agreed, but I can live with the E_STRICT solution (whether or not compat > mode is enabled), too. E_NOTICE (or E_WARNING) would be annoying to > people who have existing code with E_ALL. That's a good point. So for complete BC you drop E_STRICT and when you're going to convert to rock solid PHP 5 code you switch E_STRICT on. -- Best regards, Marcus mailto:[EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
