On Fri, 24 Mar 2000, Garrett Wollman wrote:
> < said:
>
> > The definitions of major() and minor() in sys/systm.h break usage of the
> > header. Since sys/types.h defines major() and minor() as macros which
> > compute the major and minor numbers, this creates an order dependency on
> > sys/sys
On Fri, 24 Mar 2000, Steve Kiernan wrote:
> The definitions of major() and minor() in sys/systm.h break usage of the
> header. Since sys/types.h defines major() and minor() as macros which
> compute the major and minor numbers, this creates an order dependency on
> sys/systm.h and sys/types.h.
< said:
> The definitions of major() and minor() in sys/systm.h break usage of the
> header. Since sys/types.h defines major() and minor() as macros which
> compute the major and minor numbers, this creates an order dependency on
> sys/systm.h and sys/types.h. Is this not a bad thing?
No, sinc
The definitions of major() and minor() in sys/systm.h break usage of the
header. Since sys/types.h defines major() and minor() as macros which
compute the major and minor numbers, this creates an order dependency on
sys/systm.h and sys/types.h. Is this not a bad thing?
--
Stephen Kiernan
[EMAIL