> That said, this is IMHO a hack that doesn't make the code transparent > for readers: who would know that mk_wcwidth.c is only included in > another c file, and that *this* file defines wchar_t to be something > completely different, if he sees only mk_wcwidth.c ? > > Thus, I agree with Ian: since we change it anyway, we should probably > do it the clean way and change the code directly, or add the #define > in mk_wcwidth.c at least.
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 believe that mk_wcwidth.c needs wchar_t at all, nor should it include wchar.h either. 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
