5 ms·
Has anyone seen the recent edition of Stroustrup's The C++ Programming Language book? It is 1376 pages long. This is where C# is headed as well.
by petilon 5y ago
Has anyone seen the recent edition of Stroustrup's The C++ Programming Language book? It is 1376 pages long. This is where C# is headed as well.
- pjmlp 5y agoC# was already bigger than that on C# 1.0, because when people complain about C++ they keep forgeting the standard library is part of those pages.
- tialaramex 5y agoBy a Fourth Edition Stroustrup's book devotes 400 pages of almost 1400 to the C++ Standard Library. These pages are a mix of mindless documentation you'd expect from a reference (which even in 2013 seems pretty useless as an actual book) and Stroustrup's own observations, such as on vectors: > I stopped trying to improve performance using reserve(). Instead, I use it to increase predictability of reallocation delays and to prevent invalidation of pointers and iterators. Here Stroustrup is talking about abusing vector's reserve() to assure yourself that the memory won't get re-allocated and so it's OK to point into the vector directly. Now, who wants to put their hand up to say what a good idea this is? And how about who has tried to maintain any code that was written by people who thought it was a good idea? The book would be better (not good, but better) without this "advice". The Second Edition of Stroustrup's book doesn't explain the Standard Library at all (there was in some sense no "standard library" because ISO isn't done standardising C++ when it's written) and was 700 pages in the edition I own. It's also far from a comprehensive explanation of C++ despite being so thick.
- pjmlp 5y agoAny version of .NET will top those pages, in fact it requires multiple books to discuss the whole stack.