On 02/08/2013 06:51, Sönke Ludwig wrote:
<snip>
I would seriously take into consideration to just drop the "A" versions. D is
unicode by
nature, the "W" versions are supported by all NT systems (since Windows 95
using MSLU),
and using an ANSI version of a function also just begs for bugs if typed as
"char*"
instead of "ubyte*". Many newer functions also just have a single wide string
variant.
Maybe, but there are probably a number of programs out there that still use ANSI for
backward compatibility reasons.
IMO this is just legacy cruft that was maybe still useful in times when
supporting Windows
95 was important and MSLU had to be installed as an explicit add-on, but for
nothing else
really (although frequently used in C programs because it saves typing an
additional
character: "" vs. L"" or even _T("")).
Also switching API based on a version statement always introduces a chance to
break
interoperability of two libraries that require the version to be set
differently.
<snip>
I'm not sure what else some library might reasonably define version(Unicode) to mean that
might cause a conflict....
Stewart.
--
My email address is valid but not my primary mailbox and not checked regularly. Please
keep replies on the 'group where everybody may benefit.
