On 14 May 2001 15:37:43 -0700, Sterling Hughes <[EMAIL PROTECTED]> wrote: >> We've been in that discussion before. In my opinion, we should probably >> rethink our whole deprecation approach. > > Yep, we need to decide on a standard for deprecating things. One thing I'd like to see is a utility which could check a source directory and warn about obviously deprecated / insecure / inefficient things. It'd make life easier for that hypothetical ISP admin with a large pile of code which has been haphazardly maintained for years. -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
- [PHP-DEV] Latest commit -- depreciation of call_user_metho... Sterling Hughes
- Re: [PHP-DEV] Latest commit -- depreciation of call_u... Zeev Suraski
- Re: [PHP-DEV] Latest commit -- depreciation of c... Sterling Hughes
- Re: [PHP-DEV] Latest commit -- depreciation o... Chris Adams
- Re: [PHP-DEV] Latest commit -- depreciati... Boian Bonev
- Re: [PHP-DEV] Latest commit -- depreciation o... Jani Taskinen
- Re: [PHP-DEV] Latest commit -- depreciation o... Zeev Suraski
- Re: [PHP-DEV] Latest commit -- depreciati... Jani Taskinen
- Re: [PHP-DEV] Latest commit -- depre... Andrei Zmievski
- Re: [PHP-DEV] Latest commit -- d... Cynic
- Re: [PHP-DEV] Latest commit -- d... Jani Taskinen
- Re: [PHP-DEV] Latest commit ... Peter Petermann
- Re: [PHP-DEV] Latest commit ... rasmus
- Re: [PHP-DEV] Latest commit ... Cynic