> 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. > 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. > Not that I expect the ISO definitions to change any time soon... They had better not! 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
