Ion Popescu wrote:
> Wouldn't it be easier to define StrChr as StrChr(char *, char/UChar)
> rather than StrChr(char *, Int)?
See the 3.1 docs at <http://www.palm.com/devzone/docs.html> especially
the Localized Applications chapter in the Companion book. Basically 3.1
now supports multi-byte characters (on certain devices) so the 16-bit
2nd argument to StrChr is correct. There is a new data type called
WChar (16 bits) for this purpose.
> Do you plan to support unicode?
As for Unicode, the docs show UTF-8 as a possible encoding but not full
2-byte Unicode, in the CharEncodingType enumeration. Of course they
could add 2-byte Unicode later, but that could cause a lot of
compatibility problems with older apps that may choke on the '\0' byte
in every character. Note there's a competing palm size OS that uses
2-byte Unicode and is not known for being memory efficient.
-slj-
