> There seems to be a style of header file which uses parameter names > only in the documentation above the declaration. I don't like this and > so would be happy to require all parameters to have informative names.
Actually, oxygen should complain about this when generating documentation. So yes, I think we should require all parameters to have names. > (I presume that it is still ok to have missing parameter names in > function definitions in cpp files, which serve to highlight when a > parameter is not used in the implementation.) In fact, GCC will generate warnings about unused parameters if you leave them in. -Geoff ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ OpenBabel-scripting mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbabel-scripting
