Re: E_STRICT
| From: | Jani Taskinen | Date: | Wed, 19 Nov 2003 23:08:52 +0000 |
| Subject: | Re: E_STRICT | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-5595@lists.php.net to get a copy of this message | ||
On Wed, 19 Nov 2003, Michael Walter wrote:
>> Spotting a missing function is quite easy, your script simply
>> won't work and give a clear error.. :)
>Well, not exactly :) It might just not work anymore at some time in the
>future (as you know you never really have 100% code coverage, even with
>unit testing and stuff. it's way less than 100%, actually ).
>
>I don't understand why you can't simply have a special DEPRECATELOG (or
>just entries in the CHANGELOG) which mention which functions have been
>deprecated due to which reasons, and which talks about possible
>"fixes"/replacements, tho- a simple (and hypothetical) example:
>
>[PHP 4.3.5]
>
>- strlen(): removed, as it would be redundant now that count() is
> polymorphic.
>
>So, when upgrading, you just go through the new entries, and grep your
>source files for occurences - no big deal.
>
>Where's the missing point? ;)
Err..we already do this in the NEWS..
(the opposite shows quite well in HEAD, for new functions)
--Jani