> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
