> Fabien Costantini wrote: > > > fltk.development > > Ok, If we agree that we put the the api comments in the sources cxx files > > I apologise for butting in here, but I'm not sure if this has been > addressed. If the doxygen comments are in the source files, then a user who > installed FLTK via RPMs (e.g. fltk-1.3.0-6190, fltk-devel-1.3.0-6190) > cannot refer to the installed header files for documentation? It doesn't matter where the comments are concerning where the html doc is. These are two independent things. Furthermore, the cxx AND h files will be parsed whatever we choose to put the comments into.
Last but not least, (Attention, Attention,...) I would like to emphasis the importance of gathering all class api info in ONE place. So even if suddenly, a consensus would agree in putting the api doc in H files, it is really important to me that they all stay at the *same* place, so only in headers if it was the case. Also, when I developed yesterday, a simple (still quite smart) 350+ line VB of code tool incorporated in vs2005, it was clear to me how important it was to deal with only *one* comments destination/target. I don't want to push on that subject, so even if it wasn't finally agreed that the comments would mainly be in the cxx body, i can change that provided that we keep one unique destination target ... please ! Fabien _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
