[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] [RFC][PATCH] Deprecate inb / outb.
From: |
E. Weddington |
Subject: |
Re: [avr-libc-dev] [RFC][PATCH] Deprecate inb / outb. |
Date: |
Tue, 10 Jun 2003 19:21:52 GMT |
> As address@hidden wrote:
>
> > > As address@hidden wrote:
> > > IMHO, all this would be a nice reason to finally
start
> > <compat/io.h>.
>
> > Remind me, what was supposed to go in that?
>
> All the deprecated interfaces. inb()/outb()/inp()/outp
(), ...
>
> That way, someone who wants to use their old code with
minimal changes
> could just write
>
> #include <compat/io.h>
> #include <compat/this.h>
> #include <compat/that.h>
>
> on top (or into their central #include "myapp.h"), and
get away with
> it. People writing new code will however not see the
deprecated
> interfaces in their regular header files anymore.
>
Ok, committed the macro deprecation.
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.
My fear is that if the macros get put into a seperate
header, then we'll never get rid of them.
Eric