3 ms·
>> But it's not a requirement to know all of C++ to write C++. You just need to know as much as everyone else on your team and all of the libraries that you ar
by thesuperbigfrog 3y ago
>> But it's not a requirement to know all of C++ to write C++.
You just need to know as much as everyone else on your team and all of the libraries that you are using.
"Within C++, there is a much smaller and cleaner language struggling to get out". Yes, that quote can be found on page 207 of The Design and Evolution of C++. And no, that smaller and cleaner language is not Java or C#. The quote occurs in a section entitled "Beyond Files and Syntax". I was pointing out that the C++ semantics is much cleaner than its syntax. I was thinking of programming styles, libraries and programming environments that emphasized the cleaner and more effective practices over archaic uses focused on the low-level aspects of C." Source: https://www.stroustrup.com/quotes.html#:~:text=%22Within%20C%2B%2B%2C%20there%20is,%22Beyond%20Files%20and%20Syntax%22 https://www.stroustrup.com/quotes.html#:~:text=%22Within%20C....
The question is then, "which 'cleaner and more effective practices' are being used in the code you write and maintain?"
- Night_Thastus 3y agoYou only need to know the parts you're modifying. Not everything at once.
- tempodox 3y agoOnly someone who knows too little about C++ would say something like that. Different features can interact in subtle and unexpected ways and that can bite you at runtime without any warning at compile time.
- Night_Thastus 3y agoI think that's too broad of a generalization, and I'm not following what kind of interaction you're talking about. The most obvious is if someone included a library that was dumb enough to be compiled with -ffastmath but the days of that are mostly long-gone.