Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!ficc!jeter
From: jeter@ficc.uu.net (john jeter)
Newsgroups: comp.lang.c
Subject: Re: Compilers and programming style (was Re: A question of style)
Message-ID: <Q3:2V4xds1@ficc.uu.net>
Date: 9 Jan 90 20:05:39 GMT
References: <1989Dec22.100135.2903@gdt.bath.ac.uk> <4367@rtech.rtech.com> <15065@bfmny0.UU.NET>
Organization: Ferranti International Controls Corporation
Lines: 7

In article <15065@bfmny0.UU.NET>, tneff@bfmny0.UU.NET (Tom Neff) writes:
> 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. 
                          ^^^^^^^^^^^^^^^^^^^^
A little used alternate approach is the usage of the commentary operator
in close proximity to the variable reference. ;-)