Hi all

 

I find this proposal quite frustrating… we are constantly told that we are not allowed to break existing code, even where the existing code is already broken and needs fixing.

 

Here we have a proposal that will break pretty much ever incidence of embedded code, to “fix” something that is NOT broken.

 

As Ben highlights in his post, the Read-Modify-Write paradigm, using | (or) and & (and) operators, is ingrained in the psyche – and every hardware I/O interface implements it. This proposal has zero benefit to the embedded community, and potentially a huge cost to hardware vendors.

 

In its current form, this should be rejected out of hand – and our message to C++ should be to rethink it too.

 

 

Regards

Andrew

MISRA C Liaison

 

 

From: Liaison <liaison-bounces_at_[hidden]> On Behalf Of Robert Seacord via Liaison
Sent: 22 May 2021 15:09
To: sc22wg14_at_open-std. org <sc22wg14_at_[hidden]>; liaison_at_[hidden]
Cc: Robert Seacord <rcseacord_at_[hidden]>
Subject: [wg14/wg21 liaison] n2743 Volatile C++ Compatibility

 

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/

 

Thanks,

rCs