Greg Ercolano wrote:
> 
>       The only way it might get confusing is if xyz is an action verb,
>       like "explode", in which case a programmer might accidentally code:
> 
>       // Set rocket to explode
>       rocket->explode();
> 
>       ..but all it does is return a value, and not do the action

The bright side is that you will not get a segfault later when accessing 
already exploded object.

Anyway, setting/getting functions (mostly inline) using overloading is 
fine and elegant, my small complain is with overloading the virtual 
functions. This caused this pesky shadowing - ie for draw() of Fl_Image 
classes, and redefinition of all overloads to make it public or down 
casting just to access it is so ugly...

R.

_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to