On 07/20/11 02:11, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>> Pretty sure the others would have no impact.
>
> I think adding new methods is OK. (But see above!)
> Does it change the size of the class though?
No changes in size, just adding code.
Changing the return value might be processor dependent,
I'm not sure. Some compilers might return the integer
in a register, some might return it through the stack.
Thing is any existing code wouldn't look at the return value
because its been 'void' to date, so I'm thinking if no code
checks it, nothing breaks.
If it's too dicey, making that change can wait for 1.4.
>> b) Assuming no ABI issues, any other objections?
>
> Sounds good to have - but might have to be "1.4" for now?
Yes, for anything that affects the ABI I could delay
for 1.4.
The others that don't can probably fit into 1.3.1
I'm thinking.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
