Your example shows just how accurate Widestring should be interpreted: It just only shows it is a two ore more byte sequence to represend a single character. It doesn't say anything about the content or the use of a specific (meta) encoding like UCS2 or Unicode16. If the discussion is about those two issues, you may have a point. Or two, because those are separate from a computer language point of view. The difference being: 1. compiles and 2. actually works. What I mean to say is: if the specs aren't ready, you'll have a fair chance of being mislead by assuming things that are not there (yet).

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
fpc-devel maillist  -  [email protected]
http://lists.freepascal.org/mailman/listinfo/fpc-devel

Reply via email to