On Fri, 29 Dec 2000, Ulrich Weigand wrote:
[...]
> It simply means that we will always have problems when we try to
> use either OS-dependent or CPU specific features in Windows headers.
> See e.g. my other mail on the winsock.h problems ...
It seems I missed your other mail. But anyway, 'we' have a plan for
'winsock.h'. It's outlined in bug 118:
"winsock.h should not depend on the native 'socket' headers"
http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=118
Basically the is to rewrite 'winsock.h' like we will for all the
msvcrt headers.
--
Francois Gouget [EMAIL PROTECTED] http://fgouget.free.fr/
Linux: the choice of a GNU generation
