Well, I think HeaderDoc is a good start, and would require the least amount of going back and changing old documentation.<br><br><div><span class="gmail_quote">On 10/5/05, <b class="gmail_sendername">Justin Hibbits</b> <
<a href="mailto:jrh29@alumni.cwru.edu">jrh29@alumni.cwru.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Wednesday 05 October 2005 23:04, Nathan Ladd wrote:
<br>> I recommend python scripts. I think we're going to want to integrate<br>> documentation generation with test script generation...they'll be<br>> functioning similarly and can share a lot of code.<br>><br>
> BTW I have high hopes for this ML system.<br>><br>> On 10/5/05, Justin Hibbits <<a href="mailto:jrh29@alumni.cwru.edu">jrh29@alumni.cwru.edu</a>> wrote:<br>> > What do we want to use to document our code? Currently I'm using
<br>> > HeaderDoc from Apple, but that requires Perl which I don't want to use.<br>> > We could write<br>> > our own based on HeaderDoc, using Python, but I think something else is<br>> > in order. Doxygen looks nice, but it's written in C++. Not such a big
<br>> > deal for<br>> > Gold v1, if we're just using gcc, since that has a C++ compiler.<br>> ><br>> > What are your thoughts?<br>> ><br>> > - Justin<br><br><br>Ok, we go with that. Now, in order to do that, we need to define a set of
<br>tags to use for documenting. What are required, should we model it after<br>something already, or what?<br><br>- Justin<br><br><br></blockquote></div><br>