Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!ames!ucla-cs!sdcrdcf!ism780c!tim From: tim@ism780c.UUCP (Tim Smith) Newsgroups: comp.lang.c Subject: Re: draft ANSI standard: needs your tomatoes Message-ID: <4863@ism780c.UUCP> Date: Thu, 11-Dec-86 17:37:34 EST Article-I.D.: ism780c.4863 Posted: Thu Dec 11 17:37:34 1986 Date-Received: Sun, 14-Dec-86 04:39:30 EST References: <1384@hoptoad.uucp> Reply-To: tim@ism780c.UUCP (Tim Smith) Organization: Interactive Systems Corp., Santa Monica, CA Lines: 15 > * you can declare a function to be const or volatile. Hey, this could be nice for those people who write code that changes itself. If a function is declared volatile, then the compiler could follow each instruction with a "flush instruction cache" instruction. Or the compiler could arrange to put the function in a page that is marked non-cached if the mmu supports that sort of thing. I can hardly wait for the next obfuscated C code contest... -- emordnilapregnolanalpanama Tim Smith USENET: sdcrdcf!ism780c!tim Compuserve: 72257,3706 Delphi or GEnie: mnementh