> The general rule 'docs go where the implementation is' seems > not be followed for many of Fl_Widget's methods, where docs > are in the .H, but the code is implemented elsewhere, eg: > ... > It certainly makes more sense to keep the docs > where the code implementation is, so that one can catch > discrepancies between the docs and what the code actually does.
If only it were just a case of choosing between *.h or *.cxx file, but there are quite a few functions where the doxygen comments have to go in the *.h file because there are multiple *.cxx files that contain OS-specific implementations. I added non-doxygen comments to the *.h explaining why the code was documented there and not in the *.cxx. doxygen doesn't always generate links in the *.dox for some of the drawing functions and I never managed to work out why. D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
