On Mon, Apr 10, 2000 at 12:16:50AM -0700, Francois Gouget wrote:
> Currently we're only talking about the headers but then we'll have to
> look at the link aspect.
>
> The C library would end up in two parts, one in glib.so (or whatever)
> and the other in winelibc which would contain things like _beginthread.
> Would that cause any problem?
Yes linking also needs to be discussed. My winsock example is in fact
harder than I thought. It turns out that while winsock api looks like
bsd sockets there are some major differences; basically the thing you
get back from winsock:socket() doesn't really look like an fd. The
point is that if when I link my winelib program I need socket() (and
all the other winsock functions) to link to WINSOCK_socket() not
socket(2).
Going back to includes and staying with winsock; unix stdlib.h
eventually defines the type fd_set which is rather different from
winsock's version. So even if I rewrite winsock.h I have to be
careful not to include unix's stdlib.h.
I think the thing to bear in mind is that it should be possible to
compile a Windows program to use the full Windows API with no
modifications. If the programmer then wants to add unix apis that's
fine but he clearly needs to do some work.
Huw.
--
Dr. Huw D M Davies | Clarendon Laboratory
[EMAIL PROTECTED] | Parks Road
Tel: +44 1865 272390 | Oxford OX1 3PU
Fax: +44 1865 272400 | UK
