Live data from Hacker News

On Writing a C++ Book

lospi.net

11–20 of 44 posts

Re: On Writing a C++ Book

#11

> C++ has a daunting reputation because its fundamental elements nest so tightly together Do they? I tend to find that C++’s features are often quite disjoint, which means that you can pick-and-choose which bits you want to use but the language isn’t quite designed like a coherent whole as some other languages are.

It's not a coherent language because there are so many different compilers in use today.

Many more modern Languages like Java, Python, Rust and Go have practically only one compiler/reference implementation and a couple of much less popular ones.

Re: On Writing a C++ Book

#12
post #8

Interesting that the author didn't include C++ Primer in his list of favorites. It's not perfect, but I think its latest edition (C++11) is a pretty good way to learn C++ currently.

Do you mean A Tour of C++? That's an excellent introduction by Bjarne himself, but does not talk about some things such as the Boost library.

OP is clearly talking about Stanley B. Lippman's book C++ Primer (Fifth Edition).

Re: On Writing a C++ Book

#13

> C++ has a daunting reputation because its fundamental elements nest so tightly together Do they? I tend to find that C++’s features are often quite disjoint, which means that you can pick-and-choose which bits you want to use but the language isn’t quite designed like a coherent whole as some other languages are.

It's not a coherent language because there are so many different compilers in use today. Many more modern Languages like Java, Python, Rust and Go have practically only one compiler/reference implementation and a couple of much less popular ones.

If we're talking about the language, we're talking about the standard, of which there is only one. Having many different compilers (and legacy code!) can indeed render the process of standardization hard (but needed), and legacy code can cause certain features not to be deprecated, but having several compilers do not render the language coherent or not.

Re: On Writing a C++ Book

#14
post #13

Earlier quoted context omitted.

It's not a coherent language because there are so many different compilers in use today. Many more modern Languages like Java, Python, Rust and Go have practically only one compiler/reference implementation and a couple of much less popular ones.

If we're talking about the language, we're talking about the standard, of which there is only one. Having many different compilers (and legacy code!) can indeed render the process of standardization hard (but needed), and legacy code can cause certain features not to be deprecated, but having several compilers do not render the language coherent or not.

Hm, with "the language" I meant "as used". And standard-compliance does vary somewhat. On top of the compilers, there different sub-populations of programmers, being trained on different standards, different libraries, different sets of features.

I'm not a proficient C++ programmer, but it appeared to me that there aren't that many programmers who know or even use the complete standard?

Re: On Writing a C++ Book

#15
post #2

is this out? No Starch still shows "early access" and "be ready in September", amazon showed it will be released on September 10, 2019. The TOC looks good to me. I hope it has a sample chapter.

>I’m also beyond elated that it’s getting published

I took that to mean that it is now in the process of being published.

Re: On Writing a C++ Book

#16
C++ isn't my favourite language but it does have a special place in my heart. It wasn't the first programming language I learnt (that was Visual Basic) but it was the first language I did something serious with that was used by other people.

It has been a few years since I did any C++. I looked into it when C++11 came out and it was very much like a new language with foundations of the old language I both loved and hated. Since then I haven't had a need to use it. However I have a few little side projects I want to work on and C++ would be a fine choice for most of them so perhaps I will sit down sometime and get myself acquainted with the newer standards.

Side note: I was gifted a copy of Professional C++ by Gregoire a few months ago so if anyone reading this has read the 4th edition it would be nice to know if this is a good book to get myself up to speed again or if I should look elsewhere :)

Re: On Writing a C++ Book

#17
post #2

is this out? No Starch still shows "early access" and "be ready in September", amazon showed it will be released on September 10, 2019. The TOC looks good to me. I hope it has a sample chapter.

I was able to order and download the beta ebook from No Starch this morning by following the link on his site.

Re: On Writing a C++ Book

#20
post #8

Interesting that the author didn't include C++ Primer in his list of favorites. It's not perfect, but I think its latest edition (C++11) is a pretty good way to learn C++ currently.

Do you mean A Tour of C++? That's an excellent introduction by Bjarne himself, but does not talk about some things such as the Boost library.

A tour of C++, by B. Stroustrup. Short (~250pages) and accessible introduction to the language and libraries. The second edition has been updated for C++17 and some parts of C++20.

Amazon link: https://www.amazon.com/Tour-2nd-Depth-Bjarne-Stroustrup/dp/0...

C++ Primer, by Stanley B. Lippman, Josée Lajoie, and arbara E. Moo. Really huge book, 970+ pages. Covers almost everything from the language, updated for C++11. I wouldn't use it as a beginner though.

Amazon link: https://www.amazon.com/C-Primer-Stanley-B-Lippman-ebook-dp-B...

The first one is really nice introduction, I picked it up a few months ago to learn the language. Quick read, simple to follow, I really enjoy this book. The second one works as a reference as it goes way more in details and covers a massive amount of stuff!

Post reply on HN