4 ms·
It could be misinterpreted as a user literal [1], for example with 0xAAAA_BBBB it is unclear whether _BBBB is a user literal. The original proposal discusses so
by cmovq 3y ago
It could be misinterpreted as a user literal [1], for example with 0xAAAA_BBBB it is unclear whether _BBBB is a user literal. The original proposal discusses some of the alternatives [2].
[1] https://en.cppreference.com/w/cpp/language/user_literal https://en.cppreference.com/w/cpp/language/user_literal
[2] https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3499.html https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n34...
- raxxorraxor 3y agoDidn't know about this language feature. Seems neat. The ASM integration is also neat. If you compare that to C... Still, I have rarely seen C++ compilers for embedded systems. Although the latter definition more and more includes PC hardware.
- Denvercoder9 3y ago> Still, I have rarely seen C++ compilers for embedded systems. What kind of embedded systems? Even AVR has a C++ compiler.
- raxxorraxor 3y agoYeah, that was wrong. I meant there are very few serious projects implemented in C++ for µC that are restricted memory wise. Yes, AVR has a C++ compiler, but I could imagine it doesn't support all language features. If it does it would still be discouraged to use dynamic memory allocation, which is pretty essential to leverage many advantages of object orientated languages. Of course embedded systems aren't restricted to that anymore and you are perfectly fine to use C++ for the average ARM system that isn't as restricted memory wise.
- mvladic 3y agoStill, C++ is very useful on embedded systems. This article is just about that.