Question about libwine_unicode functions and others in WINE

[Alexandre Julliard]

"Robert Shearman" <R.J.Shearman at warwick.ac.uk> writes:

> Just another thought: why don't we use the wcscat, wcslen, wcscpy functions
> 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 link
> with either msvcrt or ntdll, whichever is more convenient. Is this what
> Steven originally suggested?

The problem is that the wcs* function deal with wchar_t, and this is
32-bit on Unix. We would have to use WCHAR instead, but it would get
pretty confusing for people who know the wcs* functions, so it's IMO
better to use Windows APIs that don't have a Unix equivalent.

-- 
Alexandre Julliard
julliard at winehq.com