From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: docstrings and snarfing
Date: Sat, 15 Jul 2006 11:57:23 +1000 [thread overview]
Message-ID: <87hd1j4ol8.fsf@zip.com.au> (raw)
In-Reply-To: <29874.193.203.82.226.1152785705.squirrel@www.webmail.pawfal.org> (Dave Griffiths's message of "Thu, 13 Jul 2006 11:15:05 +0100 (BST)")
"Dave Griffiths" <dave@pawfal.org> writes:
>
> I tried running the example through the C preprocessor, and it seems
> the docstring is lost anyway:
There's some magic with a "-DSCM_MAGIC_SNARF_DOCS" to get them, then
the scripts/snarf-check-and-output-texi program picks them out from
the code. (Or something like that.) Not documented in the manual
though (alas).
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-07-15 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 10:15 docstrings and snarfing Dave Griffiths
2006-07-15 1:57 ` Kevin Ryde [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-15 18:21 dsmich
2006-07-15 21:19 dsmich
2006-07-16 21:48 ` dave
2006-07-18 17:14 ` Neil Jerram
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=87hd1j4ol8.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).