Xref: utzoo comp.lang.c++:7758 comp.lang.c:29093 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!agate!monsoon.Berkeley.EDU!dankg From: dankg@monsoon.Berkeley.EDU (Dan KoGai) Newsgroups: comp.lang.c++,comp.lang.c Subject: Re: Type Qualifier [volatile] Keywords: Qualifier, joke Message-ID: <1990May26.004845.22763@agate.berkeley.edu> Date: 26 May 90 00:48:45 GMT References: <4275@infmx.UUCP> <1990May22.124936.5727@aucs.uucp> <803@ehviea.ine.philips.nl> Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44) Reply-To: dankg@ocf.Berkeley.EDU (Dan Kogai) Organization: ucb Lines: 30 In article <803@ehviea.ine.philips.nl> leo@ehviea.UUCP (Leo de Wit) writes: >In article <1990May22.124936.5727@aucs.uucp> 880716a@aucs.UUCP (Dave Astels) writes: >|In article <4275@infmx.UUCP> briand@infmx.UUCP (brian donat) writes: >|> When would a programmer want to explicitly use the >|> 'auto' storage class? >| >|I've often wondered that myself. If you find out, let me know. Come to think there's no such storage classes as "manual", and I never heard of explicit decreation of "intern" variable. Is static opposite to auto? (maybe). If so auto must have been called "dynamic". >Today's tendency for J. Random Hacker is to prefer 'bike' storage class >to 'auto' storage class; using additional keywords like push(-bike) to >explicitly request stack allocation, or mountain (bike) for huge >stacks. The last one is not supported very well on Intel architectures. I buy it. And instead of segmentation fault, you get "flat tire", "chain is torn", etc. But in this implementation, pop sometimes dumps core :) ---------------- ____ __ __ + Dan The "obfuscunated" Man ||__||__| + E-mail: dankg@ocf.berkeley.edu ____| ______ + Voice: +1 415-549-6111 | |__|__| + USnail: 1730 Laloma Berkeley, CA 94709 U.S.A |___ |__|__| + |____|____ + "What's the biggest U.S. export to Japan?" \_| | + "Bullshit. It makes the best fertilizer for their rice" Dan Kogai (dankg@ocf.berkeley.edu)