Documenting Octave Source

[JD Cole]

   Would anyone be opposed to adding more thorough documentation to the 
Octave source code. I know when I go through the sources to try to 
implement something new, there's a lot of "discovery" going on, as with 
any large body of code. I often make comments for myself, but I would 
happily donate such comments to the project if they are correct. This 
would, of course, be somewhat of a piecemail process, I wouldn't expect 
anyone to go through each source file and comment on each function, but 
I'm sure the results would accumulate over time.
   As you have probably read, I have suggested that new Octave hackers 
use doxygen to get a better grip on class dependencies, etc. Adding 
comments in a format accepted by doxygen would definitely expedite the 
learning process, not to mention benefit bug fixing and implementation.

Any thoughts?

JD