Question about libwine_unicode functions and others in WINE
steven_ed4153 at yahoo.com
Wed Dec 3 07:54:31 CST 2003
--- Robert Shearman <R.J.Shearman at warwick.ac.uk> wrote:
> Just another thought: why don't we use the wcscat, wcslen, wcscpy
> from ntdll? AFAIK, they are completely compatible with the msvcrt
> ones with
> the same names. The lstr* calls that don't need exception handling
> can link
> to these instead. On other platforms ReactOS, Windows, etc they can
> with either msvcrt or ntdll, whichever is more convenient. Is this
> Steven originally suggested?
Yes this is what I was asking about originally and yes we should use
them internaly but the problem is wine/tools programs cant link to
ntdll or msvcrt wc* functions because they are needed to build wine. A
header file that converts libwine_unicode functions to the native wc*
functions should be enough for the most part. Sorta like the
RtlHeapAlloc->HeapAlloc wrapping that we see in kernel32.
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
More information about the wine-devel