--- Robert Shearman R.J.Shearman@warwick.ac.uk wrote:
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?
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.
Thanks Steven
__________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/