Description: ------------ I know that the Mail package in general is not E_STRICT compliant. However, we run with E_STRICT error-reporting and let our custom error-handler mute strict warnings from third-party code (PEAR etc.). This works pretty good, except when using an opcode cache like e.g. xcache. In this case, there is (at least) one kind of strict warnings cannot be caught by the error-handler, namely "Strict Standards: Assigning the return value of new by reference is deprecated" caused by code like this: $foo =& new Bar(). Apart from this, everything else works fine. Luckily there are only a few occurrences of this pattern in the PEAR packages that we use. A number of these are in the Mail and Net/SMTP packages. While there may be a marginal difference in performance, I believe these two statements are functionally identical: $foo =& new Bar(); $foo = new Bar(); Any chance the latter form could be used by Mail and Net/SMTP? As far as I am concerned, it makes no difference to PHP4 users or PHP5 users running without strict error reporting. Thanks :-)

I have no problem with this. Done in CVS, so it'll be in the next release. I'd rather not roll a release just for this, though.