Re: What about supporting E_STRICT error level?

peter fiksman wrote:

Hello all, what do you think, maybe we should pay attention on avoiding PEAR and its components to cause the E_STRICT PHP warnings? (should be mostly the "var" definition). One day we will have to branch for PHP5 only and remove PHP4 compatibility, this will allow interfaces and better overall structuring.

The current plan is to remove the E_STRICT warning on var in php 5.1.3. However there are more issues obviously that will still make it effectively impossible to write php4 and php5 compatible E_STRICT compliant code. So the only approach is php5 only code. I am pondering how to address this with MDB2. Personally I am reluctant to work on php5 only code in PEAR due to the Exception handling RFC that passed. I rather publish my php5 code outside of PEAR due to the requirement to make use of Exceptions. But yes, its time that we push for E_STRICT compliant code. For one it should be easy to distingish and search for such code. regards, Lukas