unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Allister MacLeod <amacleod@mv3d.com>
Subject: Re: Doc snarfing on C code
Date: Thu, 13 Nov 2003 14:18:51 -0500	[thread overview]
Message-ID: <20031113191851.GA681@shoggoth> (raw)
In-Reply-To: <874qx8w0gj.fsf@zagadka.ping.de>

On Thu, Nov 13, 2003 at 08:08:28PM +0100, Marius Vollmer wrote:
> Ludovic Courtès <ludovic.courtes@laas.fr> writes:
> > As of Guile 1.6, what is the recommanded method to snarf documentation
> > from C source files that use the `SCM_DEFINE' and friends macros?
> There is no, unfortunately...

Sounds like it would be a pretty simple text-processing problem,
right?  What exactly would be necessary?

Ciao,
 Allister

-- 
Allister MacLeod <amacleod@mv3d.com> | http://amacleod.is-a-geek.org/
 Elen síla lúmenn'omentielvo.


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


      reply	other threads:[~2003-11-13 19:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28 15:09 Doc snarfing on C code Ludovic Courtès
2003-11-13 19:08 ` Marius Vollmer
2003-11-13 19:18   ` Allister MacLeod [this message]

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=20031113191851.GA681@shoggoth \
    --to=amacleod@mv3d.com \
    /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).