> Widestrings need to be like that for compatibility with c and c++

Not exactly, they need to be like this because the dang MS COM.
However I can't see why is this different than the AnsiString vs
Windows PChar-based API...

> There is probably another way around that, like using a normal
> ref-counted ansistring and work with the bytes inside it.

Sure, that's one of the possibilities.

-Flávio

_________________________________________________________________
     To unsubscribe: mail [EMAIL PROTECTED] with
                "unsubscribe" as the Subject
   archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to