Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÝ<div class="post">No problem, that is why I asked about documentation before I started writing it.&nbsp; I still would like to document it though and maybe we can come to some system which you would find acceptable.&nbsp; One possible way is that I just run Doxygen on my own code and just use the auto-generated docs without adding any descriptions, etc.&nbsp; This would have no impact on the project and myself or anyone else could do this whenever but it limits the usefulness of the documentation.<br/><br/>A second, and perhaps more appealing method would be to utilize the fact that Doxygen does not require the added documentation to be in the same file as the source code it is documenting.&nbsp; We could add a single file that contains the documentation blocks with links pointing to the function names.&nbsp; Doxygen then combines this with the auto-generated info it collects from the source to produce the docs.<br/><br/>Finally, whether we use Doxygen or not, I would like to write a "man page" for the program documenting the command-line options it takes.&nbsp; Where is the command line processed in the code?&nbsp; I looked at main.cpp and didn't see it (in fact I couldn't even find the "main" function).<br/><br/>-Buck</div> text/html