From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Cc: Bruce Korb <bkorb@veritas.com>, guile-devel@gnu.org
Subject: Re: doc snarfing
Date: 31 Oct 2003 23:53:52 +0000 [thread overview]
Message-ID: <87d6cdx8tr.fsf@kanga.tapsellferrier.co.uk> (raw)
In-Reply-To: <Pine.GSO.4.21.0310311303030.3967-100000@harper.uchicago.edu>
"Peter S. Christopher" <peterc@midway.uchicago.edu> writes:
> Hi Bruce,
>
> Thanks for the feedback. I have two questions for you:
>
> a) I couldn't find any google hits for JavaDoc and C/C++; does JavaDoc
> work with C-syntax?
>
> b) Given that snarfing is ugly-ish, how does the libguile team strip
> the documentation out of the source code? Particularly, how does one fetch
> the SCM_SNARF_DOCS data from source file?
You could also use schmooz which is part of the latest editions of SLIB.
http://www.swiss.ai.mit.edu/~jaffer/SLIB.html
Nic Ferrier
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-10-31 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3FA2969B.85C516A8@veritas.com>
2003-10-31 19:09 ` doc snarfing Peter S. Christopher
2003-10-31 23:53 ` Nic Ferrier [this message]
2003-10-31 16:43 Peter S. Christopher
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=87d6cdx8tr.fsf@kanga.tapsellferrier.co.uk \
--to=nferrier@tapsellferrier.co.uk \
--cc=bkorb@veritas.com \
--cc=guile-devel@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).