MacArthur, Ian (SELEX GALILEO, UK) wrote: >> I was even considering whether mk_wcwidth() should be directly >> visible at all, and wrap it with an fl_someNameHere() routine >> anyway to keep things consistent. > > Yes - that might be the smart thing to do: then (for example) if we > decide to use platform specific functions at a later date, all that will > be hidden inside fl_wcwidth() or whatever... This function could of > course handle the "errors to cp1252" mapping and so forth too, if > required.
+1: yes, please, I like fl_wcwidth() >> If we keep MK's wcwidth.c in its vanilla state, we can swap in an >> update or replacement if it is ever needed without much fuss. > > Agree. Me, too. Maybe #include it, or at least copy it in fl_wcwidth.c(xx) and leave it as its own function (if possible). Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
