On Mon, 5 Jun 2000, Bradley Baetz wrote:
> Francois Gouget wrote:
[...]
> > I guess this is what happened. They forgot to split it to A/W when
> > they switched to Win32. So after they had to keep it with for
> > compatibility. But what type should they give it: LPCSTR or LPCWSTR. In
> > fact their doc says it automatically detects which case they are in and
> > call the proper A/W function. This is why they have put an LPVOID:
> > because it can be either LPCSTR or LPCWSTR.
>
> And I'll add a comment to that effect. Where did you get that doc from?
> I can't find it on the ms website.
From their header file actually. It contains the following comment:
* Thus for the api MCIWndCreate, there are in fact two apis,
* MCIWndCreateA and MCIWndCreateW. If you call MCIWndCreate, this will be
* re-routed to MCIWndCreateA unless UNICODE is defined when building your
* application. In any one application, you can mix calls to the
* Ansi and Unicode entrypoints.
Also they indicate this API was already there in the Win3.1 times.
Everything else is just an educated guess.
--
Francois Gouget [EMAIL PROTECTED] http://fgouget.free.fr/
The nice thing about meditation is that it makes doing nothing quite respectable
-- Paul Dean
