From: Per Bothner <per@bothner.com>
To: "David E. Weekly" <dweekly@legato.com>
Cc: Dale Johannesen <dalej@apple.com>, gcc@gnu.org
Subject: Re: -Wignored-returns?
Date: Thu, 06 Dec 2001 18:12:00 -0000 [thread overview]
Message-ID: <3C101FD2.5010605@bothner.com> (raw)
In-Reply-To: <0ba601c17ebd$1c7409d0$5c044589@legato.com>
I think the text in trouble.texi is that
"we don't think the compiler should warn
about unused return values", but I don't
read it as a refusal to provide such an
option, as long as it is not the default,
nor implicitly enabled by other flags.
So I say go ahead and submit a patch. If
the implementation is clean, I'd be in favor.
--
--Per Bothner
per@bothner.com http://www.bothner.com/per/
next prev parent reply other threads:[~2001-12-07 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 16:23 -Wignored-returns? David E. Weekly
2001-12-06 16:26 ` -Wignored-returns? Dale Johannesen
2001-12-06 16:59 ` -Wignored-returns? David E. Weekly
2001-12-06 17:12 ` -Wignored-returns? Dale Johannesen
2001-12-06 17:23 ` -Wignored-returns? David E. Weekly
2001-12-06 18:12 ` Per Bothner [this message]
2001-12-06 17:48 -Wignored-returns? dewar
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C101FD2.5010605@bothner.com \
--to=per@bothner.com \
--cc=dalej@apple.com \
--cc=dweekly@legato.com \
--cc=gcc@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).