DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L1942 Version: 1.3-current Adding a CHANGES.API file or whatever to maintain the API changes would be also error prone because we could easily forget to update it, while updating the main documentation. This said, it indeed seems to me essential to keep tracks of changes or even new functionalities, deprecated ones, and so on. I tend to believe only a fully implemented doxygen documentation could really help in that field, as doxygen tags can be added on the fly and in the sources _during_ the modification process to reflect complex doc changes. I would be interested to get Matt's opinion on this as he made a huge work on the fltk1.x documentation. Link: http://www.fltk.org/str.php?L1942 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
