Volatile is Necessary

[00704a-Liber]

In article <580 at garth.UUCP> walter at garth.UUCP (Walter Bays) writes:
>The 'volatile' keyword would also work for uniprocessor device
>drivers.  How about setjmp()?  Or side effects of functions with
>"dangerous" pointers?

setjmp() is a function call (in much the same way as fork(), exec(),
exit(), etc.) and is not part of the language specification itself (it is
not in section 3 of the draft standard).  Same is true about side effects of
functions of dangerous pointers.  'Volatile', however, IS part of the
language specification.  I consider it to be a 'frill' because nothing else
in the language specification addresses hardware, per se.
-- 
 _ __			NEVIN J. LIBER	..!ihnp4!ihlpf!nevin1	(312) 510-6194
' )  )				"The secret compartment of my ring I fill
 /  / _ , __o  ____		 with an Underdog super-energy pill."
/  (_</_\/ <__/ / <_	These are solely MY opinions, not AT&T's, blah blah blah