wxWindows: it's official!
fgouget at free.fr
Tue Jan 7 17:47:31 CST 2003
On Tue, 7 Jan 2003, Dimitrie O. Paun wrote:
> On January 7, 2003 03:00 pm, Francois Gouget wrote:
> > For exactly the same reasons, Winelib applications, using Windows paths
> > (c:\Windows\wininit.ini) on Unix have to link with the Wine C library
> > (msvcrt) rather than the native one (glibc) in order to call functions
> > with these paths.
> But this is missing the point. What you are saying is that we should
> not allow people to link to the native libc, because you think that
> the msvcrt behavior is more correct. I beg to differ.
> If people choose to ling to glibc, they must be aware the apps will not
> work with Windows paths. It's their choice.
No. I contend that applications making use of access and other similar
APIs in Winelib will not work at all unless they have been specifically
designed for that case, in which case they should not be using io.h
anyway. Thus for me adding this header has no value and will only cause
trouble due to the confusion it introduces.
You contend that Windows applications calling the glibc access function
will still work with no (related) modification (though you conceed they
may only be partially functional), thus justifying the presence of io.h.
That's where we differ.
Francois Gouget fgouget at free.fr http://fgouget.free.fr/
Linux: the choice of a GNU generation
More information about the wine-devel