On 06.11.2008, at 09:17, Albrecht Schlosser wrote: > I agree that there should be a standard proposed in the FLTK coding > standards document. However, I think that your analysis covers only > the > exceptions, because you searched only for "set_", "is_", and "ed()" as > you described in the link above.
set and clear is used for bit flags. Values don't use "set". set_changed() sets the "changed" bit but color(0) sets the color value It can be hard for non-native speakers to figure some calls out, for exmaple: maximize() vs. maximized() (setter and getter), but set_maximized() also seems awkward to me I am glad we have not hit irregular verbs yet ;-) bend() vs. bent(), for example (setter and getter, again) I can't offer a solution, unfortunatly, but I likel to read code in a somewhat meaningful English sentence. if (window->maximized()) then ... . if (window->is_maximized()) then ... . seem both OK, or should it be window->is_maximum_size()... :-/ - I really don't know. Whihever it is though, it should be mostly consistent. Matthias ---- http://robowerk.com/ _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
