From: Alexandr Vityazev <avityazev@posteo.org>
To: 49911@debbugs.gnu.org
Subject: bug#49911: [PATCH] api-control: Fix misprint in code example.
Date: Fri, 06 Aug 2021 15:06:56 +0000 [thread overview]
Message-ID: <875ywifw8f.fsf@posteo.org> (raw)
* doc/ref/api-control.texi (Simple Conditional Evaluation):
Correct the typo in the example unless form.
Delete trailing whitespaces.
---
doc/ref/api-control.texi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/ref/api-control.texi b/doc/ref/api-control.texi
index 5df5344c5..6c87811d0 100644
--- a/doc/ref/api-control.texi
+++ b/doc/ref/api-control.texi
@@ -154,7 +154,7 @@ documentation:
(define-syntax-rule (when test stmt stmt* ...)
(if test (begin stmt stmt* ...)))
-(define-syntax-rule (unless condition stmt stmt* ...)
+(define-syntax-rule (unless test stmt stmt* ...)
(if (not test) (begin stmt stmt* ...)))
@end example
@@ -1657,12 +1657,12 @@ scm_foo (SCM s1, SCM s2)
c_s1 = scm_to_locale_string (s1);
- /* Call 'free (c_s1)' when the dynwind context is left.
+ /* Call 'free (c_s1)' when the dynwind context is left.
*/
scm_dynwind_unwind_handler (free, c_s1, SCM_F_WIND_EXPLICITLY);
c_s2 = scm_to_locale_string (s2);
-
+
/* Same as above, but more concisely.
*/
scm_dynwind_free (c_s2);
@@ -2312,7 +2312,7 @@ causing a segmentation fault. Guile provides some macros to make this
easier.
@deftypefn Macro void SCM_ASSERT (int @var{test}, SCM @var{obj}, unsigned int @var{position}, const char *@var{subr})
-@deftypefnx Macro void SCM_ASSERT_TYPE (int @var{test}, SCM @var{obj}, unsigned int @var{position}, const char *@var{subr}, const char *@var{expected})
+@deftypefnx Macro void SCM_ASSERT_TYPE (int @var{test}, SCM @var{obj}, unsigned int @var{position}, const char *@var{subr}, const char *@var{expected})
If @var{test} is zero, signal a ``wrong type argument'' error,
attributed to the subroutine named @var{subr}, operating on the value
@var{obj}, which is the @var{position}'th argument of @var{subr}.
--
2.32.0
--
Alexandr Vityazev
reply other threads:[~2021-08-06 15:06 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=875ywifw8f.fsf@posteo.org \
--to=avityazev@posteo.org \
--cc=49911@debbugs.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).