The features that make C++ decent are often found in C++ 20/23, for which there are woefully few resources Especially when looking at something written for a Unix/Linux/Posix system vs Windows.Īs someone who has been painfully self-teaching C++ for the last ~1.5 years on and on, these are my hangups: And because of it's breadth, going from one C++ codebase to another could look completely different. You could work in C++ for over ten years and possibly not even encounter or use half of the functionality it provides. If anything scares off people from C++, it would definitely be the breadth of the language, though. Not saying it was the best approach at the time, but it was one option. This would be similar to partials in C# I've also worked with some code that would determine the target compilation units at build time. I've worked in codebases where the compilation units were fairly large and complex and would be implemented in separate files. Once you start throwing in preprocessor macros, meta programming, and templates, you can have a codebase that is incredibly complex to understand and maintain.Īs for the header/implementation separation, I always thought it was a good idea to have that flexibility. You can mix low level C calls with homegrown RAII frameworks, or mix traditional OOP with functional programming. It's only ugly because it was meant to be a federation of different programming paradigms.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |