Re: Making old PEAR packages (more) E_STRICT compatible

Hi, Christian Schmidt wrote:

This is a proposal on how to fix the existing PHP4-compatible PEAR packages in a way so that they remain PHP4 compatible but can also be used from PHP5 with E_STRICT error reporting enabled. It still requires some effort by the user, but at least the old packages no longer prevent people from turning on E_STRICT error reporting.

I think that's quite simple: if you want to run under E_STRICT then don't use PHP4 code. If you want to use PHP4 code then don't run under E_STRICT.

I don't know whether the inability to mute all strict errors is specific to Xcache, or whether other opcode caches have the same problem. It has been a while since a ran without an opcode cache, but AFAIR there weren't any problems back then. Also, I don't know whether there are other constructs that has to be avoided, but so far I don't think I have met any.

Did you consult Xcache developers? Did you submit a bug report for it? Why your first impulse is to "fix" PEAR for your corner case, probably breaking it for some other people?