From: Matt Sicker <boards@gmail.com>
To: 15798@debbugs.gnu.org
Subject: bug#15798: Bad variable name "noreturn" in libguile/throw.h
Date: Sun, 3 Nov 2013 17:30:39 -0600 [thread overview]
Message-ID: <CACmp6koCvF+As1Wwr9srw4KoT33WPwu0coWvWwGx5yHoucuOwA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
In the function scm_ithrow, the parameter "int noreturn" is given. Now this
works fine normally, but if stdnoreturn.h is included before throw.h (or
libguile.h more likely), then this causes a compilation error. In throw.c,
noreturn is even marked as an unused variable, so this is even more
annoying! I recommend using "no_return" to prevent any namespace conflicts.
--
Matt Sicker <boards@gmail.com>
[-- Attachment #2: Type: text/html, Size: 542 bytes --]
next reply other threads:[~2013-11-03 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 23:30 Matt Sicker [this message]
2013-11-05 0:48 ` bug#15798: Bad variable name "noreturn" in libguile/throw.h Mark H Weaver
2013-11-05 1:48 ` Jack Howarth
2013-11-05 2:47 ` Mark H Weaver
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=CACmp6koCvF+As1Wwr9srw4KoT33WPwu0coWvWwGx5yHoucuOwA@mail.gmail.com \
--to=boards@gmail.com \
--cc=15798@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).