>> Why doesn't socket.c include "ruby/win32.h"?    >> dumb question.
>
> Not a dumb question, a very valid one...
>
> ruby.h includes ruby/ruby.h
> ruby/ruby.h includes ruby/defines.h
> ruby/defines.h does include ruby/win32.h
>
> socket.c is including rubysocket.h which includes ruby/ruby.h, so it
> should be resolving properly, right?

I thought so. But I can't think Jon told lie....