Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ogicse!intelhf!ichips!inews!pima!bhoughto From: bhoughto@pima.intel.com (Blair P. Houghton) Newsgroups: comp.std.c Subject: Re: ++i++ in Plain English Message-ID: <4064@inews.intel.com> Date: 27 Apr 91 03:47:22 GMT References: <3924@inews.intel.com> <1991Apr25.174310.21264@kithrup.COM> Sender: news@inews.intel.com Organization: Intel Corp, Chandler, AZ Lines: 17 In article <1991Apr25.174310.21264@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes: >I *like* my compiler to, at times, spend lots of cycles doing loop unrolling >and elimination. It can be very useful at times. But, then, you do need >some way of saying "can't touch this," which is what volatile provides, no? Yes, you do need it, and yes, `volatile' is a hint to the compiler that you know which variables are sticky and which are just your verbosity going nuts, but there's a footnote (67) at the bottom of one page (65) of the standard (ANSI X3.159-1989) that says maybe it won't be so sticky. Of course there's lots in there to indicate this may not have been the true intent of the committee, but once again the words in print don't bear that out. --Blair "I need to wash up."