Re: RE: [PHP-QA] Re: [PHP-DEV] Re: [PHP-QA] Naming changes.

Richard Lynch wrote: > > 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... Inline, per function call: 1. @function_name... "@" supresses errors, so they can turn off the notices/warnings quickly for a single, obsoleted, function. 2. or they can: error_reporting (E_ALL^E_WARNING) obsoletefunction() error_reporting (E_ALL) Sterling also pointed out a way of doing this for all functions in a script (by making new names for them). > 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. Definitely. Note, however, that the default error level is to hide E_NOTICE, so E_WARNING will be the **first time** the name changes will be noticed by most users, and the knee-jerk reaction will to turn the reporting off/down while that code can be fixed. -Ron -- Personal: ron@opus1.com, 520-326-6109, http://www.opus1.com/ron/ Work: rchmara@pnsinc.com, 520-546-8993, http://www.pnsinc.com/ The opinions expressed in this email are not neccesarrily those of myself, my employers, or any of the other little voices in my head.