From owner-freebsd-hackers Wed Jan 5 12:27:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 8929014DAA for ; Wed, 5 Jan 2000 12:27:44 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id PAA13333; Wed, 5 Jan 2000 15:27:33 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id PAA08927; Wed, 5 Jan 2000 15:27:29 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id PAA32580; Wed, 5 Jan 2000 15:27:28 -0500 (EST) Date: Wed, 5 Jan 2000 15:27:28 -0500 (EST) From: Thomas David Rivers Message-Id: <200001052027.PAA32580@lakes.dignus.com> To: rfg@monkeys.com, rivers@dignus.com Subject: Re: [OFFTOPIC] alt. C compiler Cc: cracauer@cons.org, hackers@FreeBSD.ORG In-Reply-To: <1641.947103183@monkeys.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, according to the strict letter of the law, all of these other system > include files don't even have to exist, and if they do exist, they could > contain any garbage you want, including random binary bytes that drive the > compiler absolutely mad. The ANSI C standard has _nothing_ to say about > any system include files _except_ the very limited set that the ANSI C > standard actually mandates and talks about. > > But pragmatically, it sure would be nice if I (or you) as a programmer > developing stuff on FreeBSD could include various of the FreeBSD include > files into any program that we happen to be working on, and then fire up > the compiler (with our own personal favorite set of command line options) > and then _not_ be plagued by a whole bunch of spurious warnings and/or > errors that have noting actually to do with _our_ code. > > This isn't about standards conformance. It is about providing a top > quality _complete_ software developement system/environment. > Ok - i just wanted to be clear what exactly we're talking about. We're talking about making it easier to use the FreeBSD library code in other programs (i.e. `port' it somewhere) - presumably with a strict ANSI C compiler other than gcc. While that is certainly a laudable goal - I question the term "pragmatic". Just how often is this going to happen? Is it worth the effort? [These are questions that likely should be asked... - I'm just the Devil's advocate here..., personally - I agree... it would be nice to have "ANSI-clean" header files.] - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message