From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Cc: Guile Users <guile-user@gnu.org>
Subject: Re: literate programming
Date: 26 Jul 2004 14:23:56 +0100 [thread overview]
Message-ID: <87y8l652c3.fsf@tapsellferrier.co.uk> (raw)
In-Reply-To: <20040726130628.GH1046@backlot.linas.org>
linas@linas.org (Linas Vepstas) writes:
> On Sun, Jul 25, 2004 at 06:59:54PM +0100, Andy Wingo was heard to remark:
> > Hey folks,
> >
> > I wrote an article recently about literate programming in guile. The URL
> > is here (sorry, it's a bit long):
> >
> > http://ambient.2y.net/wingo/archives/2004/07/25/literate-programming-with-guile-lib
>
> What happens if one fails to document each and every variable?
>
> How do you tell apart other usages of "..." ?
>
> I use something similar to eguile, it embeds scheme into html,
> <html><body>Howdy <?scm (do-stuff "<h1>more markup</h1>") ?></body></html>
> Sounds incompatbile with the texinfo module.
>
> I'd like to see documentation set off with ;; (double semicolon, to
> distinguish from single semicolon). Or maybe ;! or ;-- or some other
> unique setoff.
>
> And what about "doxygen"? It works really really well for a half-dozen
> other languages and styles ... can it be extended for guile?
>
> http://www.stack.nl/~dimitri/doxygen/
Aubrey Jaffer has got an SLIB based texinfo generator that works
really well:
http://swissnet.ai.mit.edu/~jaffer/slib_4.html#SEC86
It's very similar to doxygen.
Nic
http://www.tapsellferrier.co.uk
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-07-26 13:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 17:59 literate programming Andy Wingo
2004-07-26 13:06 ` Linas Vepstas
2004-07-26 13:23 ` Nic Ferrier [this message]
2004-07-29 9:22 ` Andy Wingo
2004-07-29 10:00 ` Nic Ferrier
2004-07-26 13:28 ` Andy Wingo
2004-07-26 13:34 ` Andy Wingo
2004-07-27 3:30 ` Linas Vepstas
2004-07-29 9:18 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y8l652c3.fsf@tapsellferrier.co.uk \
--to=nferrier@tapsellferrier.co.uk \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).