From: Kevin Ryde <user42@zip.com.au>
Subject: va_end for scm_list_n, scm_c_issue_deprecation_warning_fmt
Date: Thu, 10 Jul 2003 08:08:20 +1000 [thread overview]
Message-ID: <87isqbs697.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 251 bytes --]
FYI,
* deprecation.c (scm_c_issue_deprecation_warning_fmt): Add va_end.
* list.c (scm_list_n): Ditto.
I'm not aware of any systems where a missing va_end is harmful. If
anyone knows one then this could be put in the 1.6 branch too.
[-- Attachment #2: deprecation.c.va_end.diff --]
[-- Type: text/plain, Size: 274 bytes --]
--- deprecation.c.~1.16.~ 2003-04-07 08:05:06.000000000 +1000
+++ deprecation.c 2003-07-09 17:11:49.000000000 +1000
@@ -84,6 +84,7 @@
va_start (ap, msg);
vsnprintf (buf, 511, msg, ap);
+ va_end (ap);
buf[511] = '\0';
scm_c_issue_deprecation_warning (buf);
}
[-- Attachment #3: list.c.va_end.diff --]
[-- Type: text/plain, Size: 231 bytes --]
--- list.c.~1.70.~ 2003-04-28 07:51:21.000000000 +1000
+++ list.c 2003-07-09 17:16:25.000000000 +1000
@@ -94,6 +94,7 @@
pos = SCM_CDRLOC (*pos);
elt = va_arg (foo, SCM);
}
+ va_end (foo);
return answer;
}
[-- Attachment #4: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-07-09 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 22:08 Kevin Ryde [this message]
2004-02-15 23:52 ` va_end for scm_list_n, scm_c_issue_deprecation_warning_fmt Kevin Ryde
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=87isqbs697.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).