[avr-libc-dev] Deprecation policy [was: Re: [RFC][PATCH] Deprecate inb / outb.]

[eric]

> As E. Weddington wrote:
> 
> > I don't know if I totally agree with <compat/io.h> 
> > containing deprecated macros. Isn't the whole point of 
> > deprecating macros is that they will eventually be 
removed? 
> > (At least that's what we say in the docs.) If that's 
the 
> > case, I would argue to keep them where they are. That 
way a 
> > user doesn't have to change *any* include lines. And 
then, 
> > at some point in the future remove them, as stated.
> 
> ....which will cause an outcry of the users. ;-)

So? They were adequately warned in the first place.

 
> > My fear is that if the macros get put into a seperate 
> > header, then we'll never get rid of them.
> 
> My fear is, if we leave them as they are, people will 
never
> even think about stopping to use them.  You might know 
best,
> Eric, people just /don't/ read documentation, ever. :)  So
> just documenting they are deprecated will not cause anyone
> to think about no longer using them...

In the docs, is says they are deprecated, will be removed 
in the future, and it usually gives the alternative call.

I agree in that they shouldn't be removed for avr-libc 1.0. 
It seems that on most other projects, things that are 
deprecated, eventually get removed, provided the users have 
adequate warning.

I'll leave this issue up to the admins (Ted? Marek?) to set 
policy.

Eric