DIP20: Volatile read/write intrinsics

[Alex Rønne Petersen]

On 10-10-2012 20:45, deadalnix wrote:
> Le 10/10/2012 20:31, Alex Rønne Petersen a écrit :
>> http://prowiki.org/wiki4d/wiki.cgi?LanguageDevel/DIPs/DIP20
>>
>> This supersedes DIP17.
>>
>> The primary reason to use intrinsics instead of something built into the
>> language is that the latter is too complex for current (and likely also
>> future) compiler implementations.
>>
>> Destroy!
>>
>
> We discussed it quite a lot already, but I still think volatile must be
> a qualifier of the memory, and not of the statement.
>
> In other terms, volatile should alter the way memory is read and
> written, on every access to that memory. Not on a specific statement.

I have no problem with counter-proposals so long as we get the ball 
rolling. Can you write up a counter-DIP with your idea so we can get the 
various approaches clarified and figure out which one is better?

-- 
Alex Rønne Petersen
alex at lycus.org
http://lycus.org