From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <49ccd5544bd81e479a4fa8c360d6ac1f@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun,  9 Aug 2009 17:48:27 -0400
To: 9fans@9fans.net
In-Reply-To: <4A7F3DA7.5070509@tecmav.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [9fans] Unexpected 8c warning message
Topicbox-Message-UUID: 3f3a8d0c-ead5-11e9-9d60-3106f5b1d025

> 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