4 ms·
I may come off as a bit nutty here, but do we really want to add another mechanism to C/C++ for something that has been worked with for decades? Most of these
by angersock 14y ago
I may come off as a bit nutty here, but do we really want to add another mechanism to C/C++ for something that has been worked with for decades?
Most of these issues are things you learn really fast how to avoid in production systems, using things like #pragma once, include guards, and proper symbol and header exposure when writing C libraries.
This doesn't really seem like much other than feature bloat for something that works, works well enough, and which probably won't be implemented in a timely fashion by at least 1 major compiler vendor (Hey folks! There's life outside clang and gcc and icc!).
- napierzaza 14y agoWell if you looked they are trying to improve fragility and performance. But I think your real issue is that you banged your head against to wall to learn it so why change it, right? You don't want that since you'd have to learn something new as well as the fact that you already know how to use the old stuff.