Subject: Re: how facilitate custom driver development: the cdevsw/conf.c problem
To: Chris Torek <torek@BSDI.COM>
From: Martin Husemann <firstname.lastname@example.org>
Date: 09/08/1997 07:46:20
> There are, of course, a bunch of related changes (no more separate
> bdevsw and cdevsw, the devsw array is a table of pointers, and each
> driver defines its own XXsw structure).
Which is particular cool: you can make all the driver interface functions
static and just let the structure be global visible!
Stops namespace polution, IMHO.