2 ms·
Cool. I had bought and read the whole of his Effective C++ book (after having read a few more basic books) some time after it came out. He really went into dept
by vram22 10y ago
Cool. I had bought and read the whole of his Effective C++ book (after having read a few more basic books) some time after it came out. He really went into depth with that book, and brought out a lot of issues that one needs to be aware of and take care of. Still remember that copy constructors can create extra copies of objects, placement new, etc. ... Also I heard from an editor at McGraw-Hill, that Effective C++ sold in the region of 50,000 copies.
- vram22 10y agoAlso, for anyone reading who's interested, he was or still is the editor of the Effective Software Development series of books, which I guess by now spans multiple titles (seen a few), and the series was probably envisioned because of the success of his book.
- davismwfl 10y agoGood point, guess I should've mentioned that when I responded. One of the best lessons I learned from him too was to test each target compiler to see what they really do, versus what you think they do. While I don't remember it being a direct lesson he had in the books, I picked it up from all his examples and testing, plus his talks. Seems super obvious to me now, but wasn't always.
- vram22 10y ago>test each target compiler to see what they really do, versus what you think they do Very good point.