From owner-freebsd-current Tue Mar 14 4:17: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (hda.bicnet.net [208.220.68.243]) by hub.freebsd.org (Postfix) with ESMTP id B42BE37B720 for ; Tue, 14 Mar 2000 04:16:57 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id HAA84797; Tue, 14 Mar 2000 07:21:01 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200003141221.HAA84797@hda.hda.com> Subject: Re: MAX_UID ? In-Reply-To: <00Mar14.160314est.115202@border.alcanet.com.au> from Peter Jeremy at "Mar 14, 2000 04:03:13 pm" To: Peter Jeremy Date: Tue, 14 Mar 2000 07:21:01 -0500 (EST) Cc: Bruce Evans , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If this was comp.std.c, then I'd agree that such constructs may fail > in some environments. It's not so clear that we need to worry about > this here (this being FreeBSD)... No, system headers should be sticklers to the standard to remain friendly to architectures BSD won't run on but the headers might be useful for. I can imagine non-byte addressable floating point DSPs with sizeof(char) == sizeof(double). I won't complain about the headers in a machine subdirectory. -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message