Re: RE: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] Naming changes.
| From: | Richard Lynch | Date: | Sat, 30 Dec 2000 17:31:39 +0000 |
| Subject: | Re: RE: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] Naming changes. | ||
| References: | 1 2 | Groups: | php.dev php.qa |
| Request: | Send a blank email to php-dev+get-42698@lists.php.net to get a copy of this message | ||
> We already have a capable warning system, are there sound reasons
> to add anything to PHP besides E_NOTICE then E_WARNINGs on the
> old names? Users can just change their error_reporting() in
> their .ini and/or on a per page, or per-script (or per function!)
per function?
I didn't know that was possible...
If it's not, the other options aren't all that attractive.
Users presumably have a reason for setting their error_reporting at a
certain level, and if wholesale changes to PHP function names are going to
force them to either:
not use the error_reporting they need, or
not upgrade until they and their clients alter *many* pages
Large-scale ISPs may have a lot of unhappy clients if they aren't forewarned
sufficiently that these changes are occurring.
To scale down, though, perhaps this is more feasible:
Release X:
A formal announcement to PHP-announce (does that exist still?) and
PHP-General
Documentation changes (somehow) to indicate which functions are changing
Release X+1
E_NOTICE
Release X+2
E_WARNING
Release X+3
E_ERROR
.
.
.