[ConservativeInPA]

Just being pragmatic, I only concerned myself with language standardization when porting code to another OS was a consideration. You probably don’t have that as a requirement if you are doing real-time programming targeting MBED. Even if you had a standardized version of C++, you’ll have code that is MBED dependent and if you ported it to another platform it wouldn’t work. Architecturally you should abstract everything hardware/OS dependent into its own layer. Adapter, facade and proxy design patterns are your best friends.

As for motivation for various flavors, it’s either iterative improvement in the language or some marketing guy that thinks the word “proprietary” sounds cool and is a feature. 😂

[cymbeline]

” Even if you had a standardized version of C++, you’ll have code that is MBED dependent and if you ported it to another platform it wouldn’t work.”

That’s exactly what the MBED development studio does. Dozens of targets. You select one and a tailored version of their enormous RTOS + peripheral support is produced. Compilations and linking is god-awful fast. It’s all done on a host computer the Github storage of the source code. An executable is downloaded to your PC and you download that via serial port (USB connection) to your target hardware that’s sitting beside you.

Fortunately the processor core is always Cortex so the compiler has only one target for the compiled code.