> i was thinking it could be nice if someone wrote a good doxygen tutorial for > the newsletter.. something that will include producing quality html docs, > making config files, etc. It would also be nice if such a tutorial included an explanation about _what_ exactly should be documented: only the public API (in which case the doxygen-generated docs effectively replace the BeBook), only the implementation (anything except the public headers), or both? (And also, which license text people should put at the top of their source files -- right now almost every file has a different copyright notice :-) -- Matthijs Hollemans All Your Software www.allyoursoftware.com