> Perhaps we can create a configure(1) controlled macro flag called
> "FLTK_ABI_FEATURE" that is default off, and could be used to
> #ifdef out ABI breaking features.
Oh, and in case it isn't obvious, users could configure'
this feature on (eg. 'configure --enable-abi-features')
and bu
> Looks like fltree.patch would break the ABI, so we can probably not
> apply this in fltk 1.3.x.
Good point.
Hmm, we really need a way to get ABI breaking stuff into FLTK,
because if we don't, we forget to add it later.
Also, I think a lot of people compile static, and aren't concerned
with the
