> In a way, this might be good for us, because this way we can change > the .H files to use descriptive names in the prototypes so they'll > show up in the docs, while leaving the source code parameter names > the way they are, avoiding to have to carefully search/replace those > single letter names throughout the old source.
It my mind the problem here isn't long or short names, but consistency. Imagine that the declaration in the *.H has parameters with long names, but the definition in the *.cxx file has short or missing names, and you have to write the doxygen comments in the *.cxx file. It will confuse the next person to come along if you talk about \param windowtop, but the code you see right under it says 'p' ... a la Fl_Slider::scrollvalue() Cheers D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
