From: Kevin Ryde <user42@zip.com.au>
Subject: call-with-new-thread docstring makeinfo warning
Date: Tue, 08 Jul 2003 08:00:53 +1000 [thread overview]
Message-ID: <87k7aungiy.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 135 bytes --]
FYI,
* threads.c (scm_call_with_new_thread): In docstring, use "( )"
outside @var to quieten makeinfo, and use @code.
[-- Attachment #2: threads.c.makeinfo-var-warning.diff --]
[-- Type: text/plain, Size: 553 bytes --]
--- threads.c.~1.56.~ 2003-06-19 09:41:18.000000000 +1000
+++ threads.c 2003-07-06 10:16:26.000000000 +1000
@@ -418,7 +418,7 @@
SCM_DEFINE (scm_call_with_new_thread, "call-with-new-thread", 2, 0, 0,
(SCM thunk, SCM handler),
-"Evaluate @var{(thunk)} in a new thread, and new dynamic context, "
+"Evaluate @code{(@var{thunk})} in a new thread, and new dynamic context, "
"returning a new thread object representing the thread. "
"If an error occurs during evaluation, call error-thunk, passing it an "
"error code describing the condition. "
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-07-07 22:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87k7aungiy.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).