Did I miss or there isn't a section that covers modern build systems? I would have loved to get an intro to that.
What does that have to do with C++?
Isn't that obvious? Those who do serious C++ development typically need a good build system.
On Writing a C++ Book
41–44 of 44 posts
Re: On Writing a C++ Book
#42Earlier quoted context omitted.
You mean, what's a good book for somebody who wants to learn programming with C++ as a language of choice? I'd vote for "Beginning Game Programming in C++" as a self-study book, and "Programming: Principles and Practices Using C++" if you have somebody more experienced that can help you set your environment.
Who is the author of your recommended "Beginning Game Programming in C++" book...? Sounds interesting.
Oops, I meant "Beginning C++ Through Game Programming" by Michael Dawson. It's a no-nonsense beginner programming text, geared towards people who want to learn C++ in order to make games.
Re: On Writing a C++ Book
#43Did I miss or there isn't a section that covers modern build systems? I would have loved to get an intro to that.
I was also thinking the same thing after glancing at the table of contents. I remember working with C++ while studying at grad school with instructions by two professors who quite loved the language. Even though I enjoyed the language and its STL very much, the mess of its build system and linking to other libraries is what comes to my mind whenever I think about C++. This is exactly why I never touched it again. Car…
>Cargo does a fantastic job for Rust in this regard. Rust won me over.
Cargo - that's exactly what I would love to have in C++. Probably there is something that I am just not aware of as I do not do a professional cpp development.
Re: On Writing a C++ Book
#44Earlier quoted context omitted.
Any language that grows big has that problem. My favourite example is Python, I started using it with version 1.6 and even though I only use it for small scripting tasks, always followed each release since then. It might appeal to beginners, but underneath lies a language as powerful as C++, where even the most savy will fail to remember what changed between minor releases.
As much as a like python, it is not as powerful as c++. Hence the reason you have to use cython/cpython to improve performance.
Powerful doesn't mean fast. Python is quite slow but C++ is not powerful enough to make so many things usable without -comparatively- a lot of work.
C++ is very fast and entrenched in a few markets ( gamedev, trading, etc) but that's it. As a language it is quite average, encumbered by too many features, too many corner cases.