> On 04/12/13 11:05, Albrecht Schlosser wrote:
> > Hmm, I'm not a "const and ABI specialist", I mean I don't know
> > all the implications that would arise if we changed this method.
> 
>       Ya, I'll have to double check that one, but I think changing
>       the prototypes (args, return values) of existing methods affects
> ABI,
>       but perhaps not const.. You'd think it wouldn't matter, as const
> is
>       not really a data size thing, it's just a permissions thing. But
> not sure.
> 
>       If for no other reason, macro'ing it out would allow it to
>       be investigated easily, and concurrently flagged to be part
>       of the next release.


So, are we saying we could try putting the FLTK_ABI_VERSION macro around 
as_window() and friends and try them out with the const form, and see what 
breaks?


Just asking; I think I've lost the thread of this converstaion!



Selex ES 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
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to