Date: Fri, 28 Jul 1995 20:05:01 -0500 From: rkw@dataplex.net (Richard Wackerbarth) To: Gary Palmer <gary@palmer.demon.co.uk> Cc: cvs-sys@freebsd.org Subject: /usr/include Message-ID: <v02130509ac3f365e6ad8@[199.183.109.242]>
next in thread | raw e-mail | index | archive | help
>Is that the way to go for architectural cleaness? I mean, with >multi-platform support on the horizon, do we want i386-centric files >in /usr/include/sys? I would hope not. I am in agreement with you. When we start talking multi-environment systems, /usr/include is simply the default value for "The Current Environment on This Machine" The include files for a generic compilation will come from some other directory. One of the common abstractions is to separate the "machine" characteristics from the "Operating System" characteristics. Therefore <machine/xxx.h> IS appropriate. Just because L!*ux does it wrong is no reason for us to do likewise. Besides, you can create a "compatability" directory which defines the <sys/xxx.h> as simply "include <machine/xxx.h>" ---- Richard Wackerbarth rkw@dataplex.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v02130509ac3f365e6ad8>