From: Nikita Karetnikov <nikita@karetnikov.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: Literate programming
Date: Sat, 06 Apr 2013 05:21:11 +0400 [thread overview]
Message-ID: <87y5cwxxmg.fsf@karetnikov.org> (raw)
In-Reply-To: <877gmnsq5z.fsf@gnu.org> ("Ludovic Courtès"'s message of "(unknown date)")
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
>> What do you think about literate programming [1,2,3]?
> I don’t think it’s appropriate here. We have (or should have) user doc
> for command-line tools, a manual for the API, as well as an on-line
> reference in the form of docstrings; the code itself is reasonably
> commented, I think, and in a functional style that hopefully simplifies
> reasoning a bit (I know there’s more to it than just writing functional
> code, but still, it’s better than TeX macros ;-)).
> WDYT?
Here is what I found yesterday: [1,2]. Those (texinfo ...) modules
provide various functions to generate html, pdf, and info from a single
source file. If different files are used, it's easy to end up with
undocumented code [3] or to have a documentation for nonexistent
functions [4].
There might be some problems (I've only checked a couple of functions).
Though, I hope that we'll give it a try.
The only drawback I see right now is the need to adapt the existing
modules. But I'm willing to do it.
[1] http://wingolog.org/archives/2004/07/25/literate-programming-with-guile-lib
[2] http://wingolog.org/archives/2006/11/17/high-on-sodium-vapor
[3] https://lists.gnu.org/archive/html/guile-user/2007-06/msg00046.html
[4] https://lists.gnu.org/archive/html/bug-guile/2013-04/msg00000.html
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2013-04-06 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 20:30 Literate programming Nikita Karetnikov
2013-02-04 21:52 ` Ludovic Courtès
2013-04-06 1:21 ` Nikita Karetnikov [this message]
2013-04-06 13:50 ` Ludovic Courtès
2013-04-06 15:26 ` Nikita Karetnikov
2013-04-06 17:53 ` Ludovic Courtès
2013-05-09 22:21 ` Nikita Karetnikov
2013-05-11 16:14 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5cwxxmg.fsf@karetnikov.org \
--to=nikita@karetnikov.org \
--cc=bug-guix@gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.