unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
* Guile Module Documentation
@ 2016-01-10  0:02 Alex Weiss
  2016-01-11 12:23 ` Amirouche Boubekki
  0 siblings, 1 reply; 3+ messages in thread
From: Alex Weiss @ 2016-01-10  0:02 UTC (permalink / raw)
  To: guile-devel@gnu.org

[-- Attachment #1: Type: text/plain, Size: 124 bytes --]

I've written a couple of guile modules.  What is the best way to generate documentation using the procedures docstrings?




[-- Attachment #2: Type: text/html, Size: 402 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Guile Module Documentation
  2016-01-10  0:02 Guile Module Documentation Alex Weiss
@ 2016-01-11 12:23 ` Amirouche Boubekki
  2016-01-12  1:09   ` Alex Weiss
  0 siblings, 1 reply; 3+ messages in thread
From: Amirouche Boubekki @ 2016-01-11 12:23 UTC (permalink / raw)
  To: Alex Weiss; +Cc: guile-devel-bounces+amirouche+dev=hypermove.net, guile-devel

Hi Alex!

Le 2016-01-10 01:02, Alex Weiss a écrit :
> I've written a couple of guile modules. What is the best way to
> generate documentation using the procedures docstrings?


I don't know such tool in Guile. The current pratice is to create
the documentation from scratch ie. without auto-generation.

I am very interested to work a such a tool. Using a markdown library
I wrote earlier, we might be able to create something similar to
https://github.com/dotmpe/mkdoc

I've done some exploratory work. Here is what I've got:


   ;; retrieve module by name
   (define srfi1 (resolve-module '(srfi srfi-1)))

   ;; go over public interface and print procedure name and documentation
   (module-for-each (lambda (name variable) (when (procedure? 
(variable-ref variable)) (pk name (procedure-documentation (variable-ref 
variable))))) srfi1)

Starting with that, one can create an html, txt or whatever of a module.

What about docdog as the name of the program? :)

HTH,

Amirouche aka amz3





^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Guile Module Documentation
  2016-01-11 12:23 ` Amirouche Boubekki
@ 2016-01-12  1:09   ` Alex Weiss
  0 siblings, 0 replies; 3+ messages in thread
From: Alex Weiss @ 2016-01-12  1:09 UTC (permalink / raw)
  To: Amirouche Boubekki
  Cc: <guile-devel-bounces+amirouche+dev=hypermove.net@gnu.org>,
	<guile-devel@gnu.org>

Thanks for the tip.  I might just do that.  I did find guile-tools doc-snarf.  I'm trying to work with that, before I write all my docs from scratch.

---- On Mon, 11 Jan 2016 07:23:12 -0500 Amirouche Boubekki <amirouche@hypermove.net>wrote ---- 

 > Hi Alex!
 > 
 > Le 2016-01-10 01:02, Alex Weiss a écrit :
 > > I've written a couple of guile modules. What is the best way to
 > > generate documentation using the procedures docstrings?
 > 
 > 
 > I don't know such tool in Guile. The current pratice is to create
 > the documentation from scratch ie. without auto-generation.
 > 
 > I am very interested to work a such a tool. Using a markdown library
 > I wrote earlier, we might be able to create something similar to
 > https://github.com/dotmpe/mkdoc
 > 
 > I've done some exploratory work. Here is what I've got:
 > 
 > 
 >    ;; retrieve module by name
 >    (define srfi1 (resolve-module '(srfi srfi-1)))
 > 
 >    ;; go over public interface and print procedure name and documentation
 >    (module-for-each (lambda (name variable) (when (procedure? 
 > (variable-ref variable)) (pk name (procedure-documentation (variable-ref 
 > variable))))) srfi1)
 > 
 > Starting with that, one can create an html, txt or whatever of a module.
 > 
 > What about docdog as the name of the program? :)
 > 
 > HTH,
 > 
 > Amirouche aka amz3
 > 
 > 
 > 




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-01-12  1:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-10  0:02 Guile Module Documentation Alex Weiss
2016-01-11 12:23 ` Amirouche Boubekki
2016-01-12  1:09   ` Alex Weiss

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).