Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!kth.se!cyklop.nada.kth.se!news From: d88-jwa@dront.nada.kth.se (Jon W{tte) Newsgroups: comp.sys.mac.programmer Subject: Re: For Loops, Summary Message-ID: <1991Jan23.201711.28906@nada.kth.se> Date: 23 Jan 91 20:17:11 GMT References: <6968@crash.cts.com> <20058@unix.SRI.COM> <1991Jan22.191628.29221@ux1.cso.uiuc.edu> Organization: Royal Institute of Technology, Stockholm, Sweden Lines: 17 In article <1991Jan22.191628.29221@ux1.cso.uiuc.edu> dorner@pequod.cso.uiuc.edu (Steve Dorner) writes: >>Loop variables are usually allocated in cpu registers and thus their >>value is not guarranteed outside the loop. The registers might or might >WRONG. In Pascal perhaps, but not in C. You can depend on the fact that: >The storage class of the variable has nothing to do with it, either. ALL OF the loop variables in C I've seen have had volatile values. That's because I've seen none, there aren't any ! The for construct is just a fleshed-out while... h+ Jon W{tte, Stockholm, Sweden, h+@nada.kth.se :: This article is fake. If you take it for real, the _REAL_ :: Jon W{tte will sue you for slander. So there ! Nyah ! :-)