Path: utzoo!mnetor!uunet!wyse!mikew
From: mikew@wyse.wyse.com (Mike Wexler)
Newsgroups: comp.lang.c
Subject: Re: volatile
Message-ID: <134@wyse.wyse.com>
Date: 29 Mar 88 19:35:16 GMT
References: <12578@brl-adm.ARPA> <1988Mar25.172355.348@utzoo.uucp> <588@imagine.PAWL.RPI.EDU> <1988Mar29.004454.2867@utzoo.uucp>
Reply-To: mikew@wyse.UUCP (Mike Wexler)
Organization: Wyse Technology
Lines: 10

In article <1988Mar29.004454.2867@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>... The principal problem with #pragma
>is that it is not portable, since its semantics are not standardized, but
>the sort of code we're talking about isn't portable anyway.
I would disagree that is isn't possible to write portable code that requires
volatiles. An example(possibly the only one), is the use of System V
or Berkeley shared memory.  With either of these you can have volatile
values in portable(At least to similar Unix systems) programs.  Given
this it might be useful for the Posix standard to require the C compiler
to support volatile or a volatile pragma.