On Mon, Feb 14, 2011 at 03:35:32PM +0200, Graeme Geldenhuys wrote: > "alias types" are not really new types, so will not affect var > parameters. So in my previous example, UTF16String will still be a > UnicodeString. The only difference will be that UTF16String has its > internal encoding bit set to UTF-16. > Here is a test program using latest FPC 2.4.3 showing that TMyString = > String - the compiler sees no difference between the two types. So the > same should be valid for UnicodeString vs UnicodeString(...) that have > their encoding bit set to something other than the platform default.
There is no unicodestring(...). Ansistring(...) and unicodestring are treated as different types on a Pascal level. There is a catch-all rawbytestring for deep RTL work, but you really use that as string type. See earlier discussions. -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
