On 19.04.2010, at 10:48, MacArthur, Ian (SELEX GALILEO, UK) wrote: > Is it safe to assume that all toolchains now know what a uint32_t is? > If so, that would be my favourite option.
I don't know if it would be safe, but I don't see that we use it anywhere, so this would be new. > I don't believe that mk_wcwidth.c needs wchar_t at all, nor should it > include wchar.h either. Currently it's commented out (#if 0), thus we know that it is not needed. But I looked at FL/fl_utf8.h, and there you can see that we often use "unsigned ucs" etc., and some functions return unsigned values for unicode characters, e.g.: /* F2: Convert the next UTF8 char-sequence into a Unicode value (and say how many bytes were used) */ FL_EXPORT unsigned fl_utf8decode(const char* p, const char* end, int* len); Thus, the main challenge would be to stay compatible with FLTK's internal representation of unicode (not UTF-8) characters. That dictates "unsigned" (IMHO), unless we want to change that too... (Of course we could also live with different, but compatible types, but I would prefer to make them all the same - whatever it would be eventually). Albrecht _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
