|
|
> Since this is a major release (1.4.0), we should put some priority on anything that
> affects ABI, esp. if it involves adding members to structures that can be used in
> later fixes. Sometimes thinking ahead like adding a char just for bit flags we know
> we'll need can be useful to prevent ABI breakage during the maintenance path.
There are also a bunch of non-virtual methods that could be made
virtual. I don't remember exactly what, since my list was from years
ago, but if someone has been keeping track, now is a good time to do
those changes!
Here's a fragment from an old file I was able to find:
Fl_Input_::value should be virtual
Fl_Input_::position shadows Fl_Widget::position with a different meaning.
I'm sure there are many more non-virtual functions that could be made virtual!
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/CACbaDy5FBXd0tVPcKkWE9m%3D6Qw%3D49yi2azHzhW-FaJJEr%2BF2VQ%40mail.gmail.com.
[ Direct Link to Message ] | |
|
| |