From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Unexpected 8c warning message
Date: Sun, 9 Aug 2009 17:48:27 -0400 [thread overview]
Message-ID: <49ccd5544bd81e479a4fa8c360d6ac1f@quanstro.net> (raw)
In-Reply-To: <4A7F3DA7.5070509@tecmav.com>
> It's a pity. In other - more complicated - situations I found such
> warnings appropriate and very helpful.
> Could that case be recognised during the variable-scope analysis on the
> intermediate format (tuples ?) ?
> I don't remember what D.Gries and others said about and I don't know the
> 8c internals at all.
> It's just an academic question I do for cultural interest.
> IMHO 8c is better than gcc even if sometimes it wrongly complains about
> variables use.
sure, one could perform all sorts of analysis on the code.
but i think that would be beside the point. i find that code that is subtle
enough to evoke a warning often needs to be simplified
for the benefit of other humans — or even the author in
a week.
in your case, you can either provide a dummy assignment
or use SET(var) to inform 8c that it can forget about that
warning.
- erik
next prev parent reply other threads:[~2009-08-09 21:48 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 [this message]
2009-08-10 16:24 ` Adriano Verardo
2009-08-10 16:43 ` erik quanstrom
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=49ccd5544bd81e479a4fa8c360d6ac1f@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).