Gavriel State wrote:
>
> Uwe Bonnes wrote:
> > my personal believe is that it doesn't make much sense to work more on
> > CRTDLL.
>
> What about it's use in WineLib apps? Remember, a WineLib apps's fopen
> call needs to get redirected to CRTDLL fopen, *not* glibc's fopen.
This seems an important point, but I'm not sure I fully grok it.
AFAIK, the only reason we have to use the CRTDLL fopen is
so that the file handle is known to Wine. That way, if the program
uses any non CRTDLL Windows API on the file handle, it will work.
However, in my experience, code that uses fopen() tends to only
use fwrite() and fread(). Thus, I believe that code like that would
mostly work. Further, if we're working with Winelib with code
that doesn't behave as I expect, IMHO it would be better to normalize
all of that code than to wrapper and/or reinvent glibc.
However, I speaking only from my gut sense, and not from detailed
knowledge, so please correct me where I'm wrong.
Jer
