There is also lazy-doc: <a href="http://planet.plt-scheme.org/package-source/orseau/lazy-doc.plt/1/7/planet-docs/manual/index.html">http://planet.plt-scheme.org/package-source/orseau/lazy-doc.plt/1/7/planet-docs/manual/index.html</a> (this documentation was of course generated with lazy-doc) It's far from perfect or complete, but it generates scribble doc from comments in source files, as well as simplifying the scribbling process. Sounds close to what you want. I haven't tested for a while, maybe it needs some update... Laurent <div class="gmail_quote">On Tue, Apr 5, 2011 at 20:51, Charles Hixson <<a href="mailto:charleshixsn@earthlink.net">charleshixsn@earthlink.net</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Is there there a program roughly similar to doxygen or javadoc for Scheme or Racket? I know myself to well to believe that I will document something, and keep the documentation current, unless it is right next to the code being documented. (It didn't work in Fortran or C when that's one of the things I was being paid to do, so it's not likely to work now.) But javadoc and doxygen are things I find easy to just update the documentation when I change the code. If I understand correctly Scribble wants the documentation to be in a separate file, so I need a different method. >From past history I prefer documentation embedded in comments preceding the code item that it documents. I never did take to Python documentation strings. And I'd like to be able to produce two kinds of documentation: one that documents everything and one that only documents externally visible items. My ideal output forms are HTML and odt (OpenOffice) files. _________________________________________________ For list-related administrative tasks: <a href="http://lists.racket-lang.org/listinfo/users" target="_blank">http://lists.racket-lang.org/listinfo/users</a> </blockquote></div>