draft ANSI standard: const/volatile functions

[der Mouse]

In article <4863 at ism780c.UUCP>, tim at ism780c.UUCP (Tim Smith) writes:
>> * you can declare a function to be const or volatile.

> Hey, this could be nice for [...] code that changes itself.  If a
> function is declared volatile, then the compiler could follow each
> instruction with a "flush instruction cache" instruction.

> I can hardly wait for the next obfuscated C code contest...

Or imagine if the cache-flush is privileged (eg, a VAX: mtpr $TBIA,$0)
and must be done via a syscall.  Inefficiency city....a syscall *every*
*instruction*?!

					der Mouse

USA: {ihnp4,decvax,akgua,utzoo,etc}!utcsri!mcgill-vision!mouse
     think!mosart!mcgill-vision!mouse
Europe: mcvax!decvax!utcsri!mcgill-vision!mouse
ARPAnet: think!mosart!mcgill-vision!mouse at harvard.harvard.edu