jordan@s6.Morgan.COM (Jordan Hayes) (12/17/90)
For instance, in <sys/socket.h>, there's a reference to ushort (rather than u_short), which barfs if you use -ZB ... also, in <sys/uio.h> there is no check to prevent multiple #includes of this file, so if you happen to do it, you lose. Can we post bugs like this here? Does Apple have an e-mail address to send to instead? /jordan
urlichs@smurf.sub.org (Matthias Urlichs) (12/19/90)
In comp.unix.aux, article <2395@s6.Morgan.COM>,
jordan@s6.Morgan.COM (Jordan Hayes) writes:
< For instance, in <sys/socket.h>, there's a reference to ushort (rather
< than u_short), which barfs if you use -ZB ... also, in <sys/uio.h>
< there is no check to prevent multiple #includes of this file, so if you
< happen to do it, you lose.
<
Better use ushort_t; if not, the problem will reappear with the first program
you compile without -ZB...
When fixing the include files for gcc, I convinced the fixincludes script to
also converu ushort and u_short to ushort_t (same for long, char, whatever)
and to put a "#pragma once" in front of every file. Voila, no more problems
with multiple includes.
Sorry, but I managed to misplace that fixincludes script.
I'll probably recreate it for 2.1 when it gets out.
--
Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\
Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(0700-2330) \o)/