> There are things in Xutf8.h that use int, and some unsigned int. > Do they all need to be checked too?
Probably we ought to be consistent, but *as it stands at present* either int32_t or uint32_t are fine in practice. The ISO 10646 is set up in such a way that code points throughout the 32-bit range could be used, so a uint32 would be appropriate. However, the actual Unicode ranges as currently defined, (and see RFC 3629) specify that the valid range is (currently) only up to 0x0010FFFF, so in practice an int32 is fine... I don't know what Linux or OSX use internally for their 32-bit wide char types, I guess we should try and achieve some sort of consistency of possible. I guess uint32 would be my guess? Win32 will always be an "outlier" since they use a 16-bit wchar... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
