> On Thu, 17 May 2001, Warner Losh wrote:
>
> > In message <[EMAIL PROTECTED]> Brian
> > Somers writes:
> > : Solaris calls it's ioctl files /usr/include/sys/<driver>_io.h so I'd
> > : spell digiio.h /usr/include/sys/digi_io.h.
> >
> > Actually, the more I think about it, the more I like putting it in
> > /usr/include/sys/fooio.h. We have lots of other files there now. The
> > down side to this approach is that it breaks up the driver sources
> > that we've been trying to concentrate into sys/dev/foo/* (or
> > introduces asymetry such that you can't just toss in a -I/sys and have
> > the same tree that gets stuck under /usr/include).
>
> I quite like the fact that the programming interface <sys/fooio.h> is
> separated from the driver implementation. There is less chance that the
> driver writer will expose irrelavent implementation details in the API,
> which in turn makes for a more stable ABI.
I agree, and what's more, bde hasn't disagreed to any such
suggestions....
> --
> Doug Rabson Mail: [EMAIL PROTECTED]
> Phone: +44 20 8348 6160
--
Brian <[EMAIL PROTECTED]> <brian@[uk.]FreeBSD.org>
<http://www.Awfulhak.org> <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
