Hi,
This has been discussed before but I'm not sure we have a conclusion.
Windows has its set of 'standard' includes which differ somewhat from
glibc. For example wcslen in declared in string.h and wchar.h in a
Windows environment whereas glibc declares it only in wchar.h .
Therefore a program that under Windows might include string.h will not
cleanly compile as a WineLib program. Other examples of this are
additions to the standard such as _fullpath which is declared in
stdlib.h. How are we going to deal with this?
Another related question is winsock.h . Some of the standard socket
functions have different arguments than their unix counterparts
(eg. getpeername()'s 3rd arg is socklen_t * in unix and int * in
Windows). At the moment winsock.h includes the unix headers at the
top which means that these prototypes don't match the Windows ones.
Should winsock.h be rewritten to not include these headers?
Huw.
--
Dr. Huw D M Davies | Clarendon Laboratory
[EMAIL PROTECTED] | Parks Road
Tel: +44 1865 272390 | Oxford OX1 3PU
Fax: +44 1865 272400 | UK
