On 20.07.2011 11:11, MacArthur, Ian (SELEX GALILEO, UK) wrote: > > These sound like useful additions to me... > >> A few questions: >> >> a) Does (1) break the ABI (by changing the return value >> from void to int)? > > I think it does, but I am usually wrong about ABI stuff..
Yes, I'm pretty sure this would change the function signature (name mangling), and that alone is an ABI change. >> Pretty sure the others would have no impact. > > I think adding new methods is OK. (But see above!) Yep, unless they are virtual. > Does it change the size of the class though? That might be an issue... > Argh, I always get this wrong... The size of the class is detemined by the number (and maybe order, because of alignments...) of member variables (order alone matters too, of course WRT ABI). New methods alone don't change any of this. >> b) Assuming no ABI issues, any other objections? > > Sounds good to have - but might have to be "1.4" for now? +1 for 1.4 - maybe non-ABI-breaking methods now? Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
