Re: Obsolete functions and variables

[Mike Mattie <codermattie@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

On Fri, 11 Apr 2008 11:45:50 +1200
Nick Roberts <nickrob@snap.net.nz> wrote:

>  > >>  I guess the dangers generally outweigh the advantages but
>  > >> there's not much point in marking them obsolete if they're
>  > >> never going to be removed.
>  > > 
>  > > I agree. I just don't expect it to happen.
>  > 
>  > 
>  > I am not sure I agree. Are not a function sometimes marked as
>  > obsolete because there is a new better version that works in more
>  > cases? The old obsolete function may still work in many cases.
> 
>   Obsolete \Ob"so*lete\, a. [L. obsoletus, p. p. of obsolescere.
>      See {Obsolescent}.]
>      1. No longer in use; gone into disuse; disused; neglected;
> 
> Hmm, this is starting to sound like Monty Python's dead parrot sketch!
> 
>  > Maybe a more visible warning when obsolete things are found would
>  > be good? (Using for example lwarn.)
> 
> How would this work?  Not in some hand wavy way but with a real code
> explanation.
> 

If I need something really visible I inject it into the scratch buffer
as a comment. I Never miss that.

Cheers,
Mike Mattie

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]