From: "David E. Weekly" <dweekly@legato.com>
To: "Dale Johannesen" <dalej@apple.com>
Cc: <gcc@gnu.org>
Subject: Re: -Wignored-returns?
Date: Thu, 06 Dec 2001 16:59:00 -0000 [thread overview]
Message-ID: <0b8101c17eb8$8dcdedd0$5c044589@legato.com> (raw)
In-Reply-To: <903FC75A-EAA8-11D5-8923-003065C86F94@apple.com>
Dale,
Thanks for your prompt response, even if it's one that makes me sad.
I don't really understand why GCC refuses to allow its users to specify this
option. I perfectly understand not including it in -W or -Wall, but not even
permitting this option to be made seems to be more about enforcing the
particular tastes of the GCC developers than it does actually providing a
useful compiler for users. ("Coming as I do from a Lisp background, I balk
at the idea that there is something dangerous about discarding a value" was
the excuse given.) It's rather patronizing to have the GCC developer team
tell us what coding style we want to use.
With the addition of this singular warning, we could completely eliminate
lint and lclint from our development environment, saving us a whole lot of
money. [sigh] It may be trickier without this simple feature.
All the same, I have the deepest of gratitude towards the GCC development
team for making an immensely powerful toolchain for nearly all of the
platforms out there.
-david
PS: Dale, if GDB on OS/X 10.1.1 is itself segfaulting and getting "internal
error"s right and left, are you the man with whom to speak?
----- Original Message -----
From: "Dale Johannesen" <dalej@apple.com>
To: "David E. Weekly" <dweekly@legato.com>
Cc: "Dale Johannesen" <dalej@apple.com>; <gcc@gnu.org>
Sent: Thursday, December 06, 2001 4:22 PM
Subject: Re: -Wignored-returns?
On Thursday, December 6, 2001, at 04:11 PM, David E. Weekly wrote:
> GCC Team,
>
> Hello! I saw in the GCC Bug mail archives a post that a certain Gray
> Watson
> had proposed in 1992 for warning on ignored return values:
> http://www.geocrawler.com/mail/msg.php3?msg_id=1968564&list=356. Such a
> warning flag would prove invaluable for myself and for others seeking to
> wholly replace lint with GCC warning flags and seems trivial to implement.
> Is this feature already in GCC or has it yet to be added?
See "Certain Changes We Don't Want To Make" in trouble.texi.
next prev parent reply other threads:[~2001-12-07 0:47 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 ` David E. Weekly [this message]
2001-12-06 17:12 ` -Wignored-returns? Dale Johannesen
2001-12-06 17:23 ` -Wignored-returns? David E. Weekly
2001-12-06 18:12 ` -Wignored-returns? Per Bothner
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='0b8101c17eb8$8dcdedd0$5c044589@legato.com' \
--to=dweekly@legato.com \
--cc=dalej@apple.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).