On Thu, Oct 03, 2002 at 12:26:53AM -0400, Matt Fowles wrote: > I don't like Java that much (for many reasons), but I have nothing but > respect for the massive amount of documentation that is easily accessible as > a direct result of JavaDoc. I personnaly feel that it greatly helped java > achieve the success it has. If all of parrot's module were that well > documented and that easily accessible, it would be a great boon in > recruiting followers. > > Also, localizing the code and the documentation allow programmer to keep > updated documentation more easily. Furthermore, since the docs will be in > the same files as the code, we can simply refuse to accept patches that do > not update the infile documentation. Thus preventing the horribly > problematic outdated documentation.
POD has all the above attributes. Any documentation format for Parrot must unquestionably allow inlining with the code. > I say all of these things as someone who is new to this project and doesn't > know POD. If some of my statements here are in ignorant of the way things > are, please correct me. -- Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One Do you have a map? Because I keep getting lost in your armpits.
