🚀 go-pugleaf

In article <1bmqp8INN20s@uwm.edu> xepo@csd4.csd.uwm.edu (Scott R Violet) writes:
>
>Hi,
>	Last night I was playing around with sockets and needed the
>in_addr structure that is defined in the file <netinet/in.h>, of
>course now it is in the direcotry /NextDeveloper/headers/bsd.  But
>anyway, when I included this file I got errors in the header file upon
>compilation.  The errors were on line 116,117,118, and 179 (I don't
>have them handy, but I am pretty sure that the numbers are correct,)
>and the errors were u_char, u_short, and u_long undefined...  How
>would such an error come up?  The only remedy I could come up with was
>to edit the in.h header file and stick in the line 
>#import <sys/types.h>
>	Why should I have had to do that?  Am I missing something, or
>is it another bug?

No, it quite common to need multiple header files in order to make a
particular function work, and sys/types.h is a real common one to
require. For example, if you look at the man page for socket you'll see
that it says:
	#include <sys/types.h>
	#include <sys/socket.h>

You shouldn't be modifying the headers, you should just be including
both sys/types.h and in/in.h.