[Libreoffice] gbuildized xml2cmp breaks Windows

[Michael Stahl]

On 15.09.2011 11:13, Tor Lillqvist wrote:
> OK, clearly the time now has come to get rid of uwinapi completely.
> Our uwinapi.dll only contains four functions nowadays: snprintf,
> snwprintf, vsnprintf and vsnwprintf. We should move those to sal or
> something. And for those pesky binary extensions that might want an
> ABI stable uwinapi.dll, let's just keep around one from 3.3 or 3.2
> times and include it in the installer.
> 
> Fridrich shares my thoughts about this.
> 
> --tml

but moving the functions to sal will not help at all with the circular
dependency problem, it will just create a new problem with backward
compatibility.

why are the remaining functions still there?

AFAIK uwinapi is a library that contains functions that are available in
win32 but where the implementation is buggy on some version of
Windows(R); the intent was to ship a corrected version so client code
doesn't have to work around the bugs.

i think somebody once told me that the last remaining functions are only
required on Windows 2000, and if we raised the baseline to Windows XP
then it would be unnecessary.  any idea if that is true?

-- 
Theorem: All positive integers are interesting.
Proof:	 Assume the contrary.  Then there is a lowest non-interesting
         positive integer.  But, hey, that's pretty interesting!
         A contradiction.