Date: Thu, 13 Jul 2000 18:35:57 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Wilbert de Graaf <wilbertdg@hetnet.nl> Cc: FreeBSD-hackers <FreeBSD-hackers@FreeBSD.ORG> Subject: Re: #include question: <netinet/in.h> requires <sys/socket.h> Message-ID: <20000713183557.A25571@fw.wintelcom.net> In-Reply-To: <396E5A9E.E7CD05F1@hetnet.nl>; from wilbertdg@hetnet.nl on Thu, Jul 13, 2000 at 05:11:10PM -0700 References: <095401bfec6f$495ba110$0a00a8c0@alias> <20000712221526.L25571@fw.wintelcom.net> <396E49D4.DBBA9B5C@hetnet.nl> <20000713160251.Z25571@fw.wintelcom.net> <396E5A9E.E7CD05F1@hetnet.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
* Wilbert de Graaf <wilbertdg@hetnet.nl> [000713 17:11] wrote: > > Hi Alfred, > > > you might as well unconditionally include sys/socket.h and let it's > > internal #ifndef take care of that problem. > > you're right and i'll change it > > > I'm not sure why you don't just make your own new header file for > > this struct unless you're adding to an existing structure in > > socket.h, even if you are you can put whatever it is that you added > > to netinet/in.h into a seperate header or sys/socket.h itself. > > The reason is that the structures, socket options have to be in > whenever <netinet/in.h> is included, since that's what's specified by > that draft (which is good for portable code). So effectively the standard mandates this? You might as well get rid of netinet/in.h then and include it all in sys/socket.h... or... wrap your stuff in sys/socket.h like so: #ifdef _NETINET_IN_H_ /* stuff that depends on netinet/in.h */ #endif -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000713183557.A25571>