> > Also, if we are going to break the 1.1 ABI, do we want to > re-name some > > of the more inaccurately named functions and methods whilst > we are at it? > > My recommendation would be to rename them and provide the old names > as inline methods/functions that are flagged as deprecated. Then if > (*if*) we did another minor/major release we could remove them.
Can the "old names" have #warnings (or something) attached so they will throw a caution at compile time? I know a lot of my x86 Mac stuff does that, and whilst it is really annoying, it has helped me tidy things up...! SELEX Sensors and Airborne Systems Limited 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
