Re: Re: E_STRICT

From: Date: Sat, 10 Jul 2004 12:15:33 +0000
Subject: Re: Re: E_STRICT
References: 1 2 3 4  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-31828@lists.php.net to get a copy of this message
> >>So to conclude I still think that PHP5 only packages should be E_STRICT, > >>but I also think that E_STRICT compliance alone is no reason to fork off > >>a package. > Especially since a conditional include with var replaced with protected > would get you to E_STRICT just as easily. If these changes really are so minimal, wouldn't it perhaps work to create a package called say, PHP5::include, which does just that and includes the file. Sure, it might be a tad slower then including an already E_STRICT package, but an on-the-fly conversion of E_ALL-php4 code to E_STRICT-php5 code could be done, with a mix of the Tokenizer and eval(), no? Cipri

« previous php.pear.dev (#31828) next »