In message <199410081158.HAA07012@Collatz.McRCIM.McGill.EDU>,
	der Mouse writes:
>We must have different conventions.  The convention I use is that
><sys/types.h> is included after any headers involving fewer than 11
>characters between the brackets and before any involving more than 11,
>and in no particular order relative to others involving exactly 11.  It
>is then the responsibility of each include file - <sys/...> or not - to
>include anything else it needs.  Where necessary, this is arranged by
>putting copies in my shadow tree.

bleah. the only 'convention' that will work on every UNIX system i've
ever written code on is to include sys/types.h *first*, if you're going to
be including *anything* from sys/. doing anything else is st00pid, and will
break on some system or another.

bending over backwards to have NetBSD avoid this problem is silly, since
any programs that don't include sys/types.h first are far more broken than
the includes.

--
                    ----------------------------------------
-------------------// jason downs // downsj@CSOS.ORST.EDU //------------------
                   ----------------------------------------      JD105
    SunOS 4.1.3: An OS with more bugs than NetBSD, and no hope of them ever
				 getting fixed.