Re: cvs: pear /MDB2 MDB2.php package.php package_ibase.php package_mysql.php package_mysqli.php package_oci8.php package_pgsql.php /MDB2/MDB2/Driver
ibase.php mysql.php mysqli.php oci8.php pgsql.php
| From: | Lukas Kahwe Smith | Date: | Mon, 24 Sep 2007 07:08:04 +0000 |
| Subject: | Re: cvs: pear /MDB2 MDB2.php package.php package_ibase.php package_mysql.php package_mysqli.php package_oci8.php package_pgsql.php /MDB2/MDB2/Driver ibase.php mysql.php mysqli.php oci8.php pgsql.php |
||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-48150@lists.php.net to get a copy of this message | ||
Lorenzo Alberton wrote:
I know. Reading pear-dev and pear-cvs [1] I thought it was the reached consensus (it's been already applied to a number of important packages, including DB [2], Mail [3] and Net_SMTP [4]) I've already restored the one case where a reference was really needed. If problems arise, we may change back.Well you could introduce an if/else for this case. But I guess all the isError() calls will trigger E_STRICT warnings anyways. Not sure about the idea to filter these out in an error handler. Why even set E_STRICT in that case? I guess the idea could be to always check if the file originated from a knon PHP4 package. This way one could get the benefit of E_SRICT checking for packages that can/should comply while still beng able to run good old PHP4 code ... regards, Lukas