aaron wrote: Hi,
Maybe it's just me, but I always include the fundamental .h files first, so usually in this order (more or less): #include <sys/param.h> #include <sys/types.h> ... (networking stuff) #include <unistd.h> #include <stdio.h> So perhaps this is why I never saw this. It is a simple philosophy and so far hasn't caused me any trouble. :-) Not sure how it works in the Windoze environment, but then again... Not interested ;-) Hope this helps... Andy >Hi! > >I am just trying to write a simple IPv6 socket app. >after #including <netinet/in.h> I noticed that I have to include <sys/types.h> >BEFORE <netinet/in.h> which struck me as rather strange... > >Should not .h files include the depending .h files themselves so that all >dependencies of type / struct / #define definitions are met automatically? > >If not this is not what we want then we have the following problem: > >#include <sys/types.h> >#include <netinet/in.h> > > works > >but > >#include <netinet/in.h> >#include <sys/types.h> > >does not work. > >... hm... wondering if this what we want.... > >aaron. > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
