From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Unexpected 8c warning message
Date: Mon, 10 Aug 2009 12:43:21 -0400 [thread overview]
Message-ID: <eb42bda6b242c29b771a38acec3032ca@quanstro.net> (raw)
In-Reply-To: <4A8049D6.3000207@tecmav.com>
> Absolutely true.
> But I got a subtle compiler message about a very very simple and short
> piece of code.
how is the compiler supposed to determine if the code in question
is short and simple?
> > in your case, you can either provide a dummy assignment
> > or use SET(var) to inform 8c that it can forget about that
> > warning.
> >
> I didn't know SET(var) so I used a dummy assignment, as you can see in
> my original mail.
> Both seems to me a medicine worst than the disease. Personal opinion, of
> course.
on the other hand, if you've been following along at home
with linux development, you'll remember that a week or so
ago a really smart compiler screwed everybody over by optimizing
away a test for null because clearly that couldn't happen.
http://lwn.net/Articles/342330/
http://lwn.net/Articles/342420/
(this problem is also demonstrates one reason mixing
asignments and declarations is bad practice.)
- erik
next prev parent reply other threads:[~2009-08-10 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 19:33 Adriano Verardo
2009-08-09 19:46 ` Russ Cox
2009-08-09 21:20 ` Adriano Verardo
2009-08-09 21:48 ` erik quanstrom
2009-08-10 16:24 ` Adriano Verardo
2009-08-10 16:43 ` erik quanstrom [this message]
2009-08-10 17:19 ` Russ Cox
2009-08-10 23:30 ` Adriano Verardo
2009-08-11 0:19 ` Charles Forsyth
2009-08-10 20:33 ` Adriano Verardo
2009-08-10 21:01 ` James Tomaschke
2009-08-11 10:30 ` Ethan Grammatikidis
2009-08-11 22:16 ` James Tomaschke
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=eb42bda6b242c29b771a38acec3032ca@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).