Date: Sat, 22 May 2021 16:48:57 +0200
Am 22.05.21 um 16:08 schrieb Robert Seacord via Liaison:
> I'm looking for reviews / comments for n2743 Volatile C++ Compatibility
> before submission. If you are interested in reviewing, you can find a
> PDF of the proposal here:
>
> http://robertseacord.com/wp/2021/05/22/volatile-c-compatibility/
> <http://robertseacord.com/wp/2021/05/22/volatile-c-compatibility/>
>
> Thanks,
> rCs
People use compound operators, increment and decrement on memory-mapped
I/O registers.
The justification of basically 'compound operators are misleading, since
they look as if there was only one memory access instead of a read
followed by a write' seems very weak to me. Users of volatile tend to be
working close to the hardware, knowing how the hardware works.
The remaining rationale apparently is just 'C++ removed the feature, so
we should, too', which also seems a rather weak one to me.
Philipp
> I'm looking for reviews / comments for n2743 Volatile C++ Compatibility
> before submission. If you are interested in reviewing, you can find a
> PDF of the proposal here:
>
> http://robertseacord.com/wp/2021/05/22/volatile-c-compatibility/
> <http://robertseacord.com/wp/2021/05/22/volatile-c-compatibility/>
>
> Thanks,
> rCs
People use compound operators, increment and decrement on memory-mapped
I/O registers.
The justification of basically 'compound operators are misleading, since
they look as if there was only one memory access instead of a read
followed by a write' seems very weak to me. Users of volatile tend to be
working close to the hardware, knowing how the hardware works.
The remaining rationale apparently is just 'C++ removed the feature, so
we should, too', which also seems a rather weak one to me.
Philipp
Received on 2021-05-22 09:49:02