Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!bfmny0!tneff
From: tneff@bfmny0.UU.NET (Tom Neff)
Newsgroups: comp.lang.c
Subject: Re: Compilers and programming style (was Re: A question of style)
Message-ID: <15065@bfmny0.UU.NET>
Date: 4 Jan 90 13:59:24 GMT
References: <1989Dec22.100135.2903@gdt.bath.ac.uk> <4367@rtech.rtech.com> <1989Dec31.153241.16479@gdt.bath.ac.uk> <649@codonics.COM>
Reply-To: tneff@bfmny0.UU.NET (Tom Neff)
Lines: 10

If you have a specialized systems/hardware-type situation where merely
referring to a variable has useful side effects, then you can cast it
to (void) or some such, to make this obvious.  Otherwise, it's probably
a coding error and lint should catch it.

The issue of how much of lint's work the c compiler ought to do is a
separate one.
-- 
Annex Canada now!  We need the room,    \)      Tom Neff
    and who's going to stop us.         (\      tneff@bfmny0.UU.NET