Xref: utzoo comp.lang.c:26386 gnu.gcc.bug:2037 gnu.g++.bug:1534 Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!deimos!ux1.cso.uiuc.edu!tank!mimsy!mojo!mojo!djm From: djm@eng.umd.edu (David J. MacKenzie) Newsgroups: comp.lang.c,gnu.gcc.bug,gnu.g++.bug Subject: Re: ANSI-fied headers for gcc Message-ID: Date: 28 Feb 90 00:45:43 GMT References: <17794@duke.cs.duke.edu> <25EAFC22.967@paris.ics.uci.edu> Sender: news@eng.umd.edu (The News System) Distribution: usa Organization: University of Maryland Lines: 21 In-Reply-To: rfg@ics.uci.edu's message of 27 Feb 90 22:16:02 GMT In article <25EAFC22.967@paris.ics.uci.edu> rfg@ics.uci.edu (Ronald Guilmette) writes: > Whenever the GNU C library becomes available, it is my understanding that > it will come with a set of include files of its own. I can only hope that > these will be tested with g++ (and with cfront) and that they will be > compatible with those. (I'm willing to help test for compatability when > the time comes.) I've seen the development sources to the GNU C library. It is ANSI (and POSIX) conformant, but uses some clever ifdefs to generate prototypes on __STDC__ and declarations on traditional C compilers. I haven't tried using it with C++. Roland McGrath is taking great pains to make it portable, though. > Also, one must assume that when there is a GNU kernel, that *it* will > also come with its own include files. Again, I hope that these will be > provided in a form that is compatible with gcc, g++ and cfront. The GNU kernel will probably be based on Mach, for whatever that's worth. -- David J. MacKenzie