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

"mayayana" <mayaXXyana1a@xxxxxxxxxxxxxxxx> wrote in message
news:D4vfe.9555$7F4.9011@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > > If you have Matthew Curland's Advanced Visual
> > > Basic 6 book, see the "Unicode conversions"
> > > section starting on page 360. VB *is* unicode.
> > > It's just converting to ANSI on either end, for
> > > convenience. But StrPtr(string) is pointing to
> > > a unicode string.
> >
> > I do not have Curland's book.
> >
>
> He explains there that VB is Unicode "inside" but
> that it was decided to make it ANSI on the surface
> for convenience. As a result, VB normally calls
> "A" versions of APIs and is actually converting
> your given string to unicode, for it's own purposes,
> then back to ANSI again for the API call. So if you
> need to make a W call you can use StrPtr because
> StrPtr is pointing to the beginning of the actual
> unicode string that VB is using. In other words,
> your variable, for instance, s2, returns an ANSI
> string when you read it, but VB is storing it as unicode.
> So StrPtr(s2), which is a pointer to the actual string
> data, is pointing to a unicode string.

Thanx, I knew that.

What I don't know is whether there are issues with "A" API calls when the
code is run in Win 95/Win 98/Win Me.
GetProcAddress may be a non-issue, could be a documentation error in the Oct
2001 MSDN Library, or not.

I've not worried about this before. But now I have written a VB 6 program
that creates a Word template from scratch (sets reference, sets password,
creates toolbar/menu and inserts code), and installs the referenced DLL.
Works with Word 97 and up, tho I may drop Word 97 if I decide to include
code in the DLL that will not run in Word 97.


.

Relevant Pages

  • Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
    ... that it was decided to make it ANSI on the surface ... for convenience. ... StrPtr is pointing to the beginning of the actual ... unicode string that VB is using. ...
    (microsoft.public.vb.winapi)
  • Re: Common Lisp spec from ANSI - they are lost!
    ... years the TeX sources have been on public FTP. ... ANSI endorsement but maintained acknowledgment)? ... So it's likely that ANSI has also, only with less publicity. ... converting it for your own use, or for a small selected group. ...
    (comp.lang.lisp)
  • Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
    ... >> then back to ANSI again for the API call. ... >> unicode string that VB is using. ... is pointing to a unicode string. ... > creates toolbar/menu and inserts code), and installs the referenced DLL. ...
    (microsoft.public.vb.winapi)
  • Re: SaveSetting and Unicode
    ... otherwise it returns the question mark to the fist ... convert a unicode string to ANSI it's going to ... translating characters from unicode to ANSI and not ...
    (microsoft.public.vb.general.discussion)
  • Re: Amazon used lisp & C exclusively?
    ... and the fact that the compiler doesn't actually catch you ... | An integer may be converted to any pointer type. ... So converting an integer to a pointer is not illegal code and well defined ... in ANSI C, but the result is implementation defined. ...
    (comp.lang.lisp)
Loading