Re: Microsoft Layer for Unicode on Windows 95/98/Me systems

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: "TC" <aatcbbtccctc@xxxxxxxxx>
Date: 8 May 2005 22:54:14 -0700

J French wrote:

(snip)

> Do you honestly think that the name of an exported procedure within a
> DLL would be in Unicode ?

Umm, maybe jumping in where I know little, but: What is wrong, in
principle, with a procedure having a unicode name? Would it not be
good, in principle, if foreign developers could name procedures using
their own language and script?

Cheers,
TC

.

Follow-Ups:
- Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
  - From: Sam Hobbs
- Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
  - From: J French

References:
- Microsoft Layer for Unicode on Windows 95/98/Me systems
  - From: Howard Kaikow
- Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
  - From: J French
- Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
  - From: Sam Hobbs
- Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
  - From: J French

Prev by Date: Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
Next by Date: Re: VB 6 install / run on Win x86-64 OK?
Previous by thread: Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
Next by thread: Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
Index(es):
- Date
- Thread

Relevant Pages

Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
... >> Do you honestly think that the name of an exported procedure within a ... >> DLL would be in Unicode? ... >good, in principle, if foreign developers could name procedures using ...
(microsoft.public.vb.winapi)
Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
... > Umm, maybe jumping in where I know little, but: ... with a procedure having a unicode name? ... > good, in principle, if foreign developers could name procedures using ...
(microsoft.public.vb.winapi)
Re: Call C DLL from VB.net-problem..array gains 4 bytes!
... No, Unicode strings don't, by definition, have a header with the size. ... you're writing code in C++, for example, the only difference between an ANSI ... which take an array of bytes. ... > Remember the DLL declaration... ...
(microsoft.public.windowsce.app.development)
Re: passing a string to a dll
... bool DLLRect::PullWhisker ... The interface for the DLL exported function could be like so: ... based on _UNICODE flag, e.g. ... I think that in these days those ANSI strings are something from the ...
(microsoft.public.vc.mfc)
Re: Populating CString in Win32 dll interface that accepts LPCTSTR
... ReleaseBuffer() if I actually modify the buffer after GetBuffer is called ... But the OP wanted the string to be "populated" by the DLL. ... Unicode or ANSI string, but the DLL might think it is a non-const pointer to an ANSI ...
(microsoft.public.vc.mfc)