3 ms·
I thought Lippman's book was adequate. And if you're familiar with the implementation of various statically-typed object models (oxymoron?) then you can see a f
by mahmud 16y ago
I thought Lippman's book was adequate. And if you're familiar with the implementation of various statically-typed object models (oxymoron?) then you can see a few ways suggest themselves.
Depends on what you want to do with this knowledge. If you want to use this knowledge for gains in performance, you will have to get your hands dirty and dig into specific implementations.
- eliasmacpherson 16y agoI guess I'm complaining more about the reader than the writer. It does provide a useful approach to test specific implementations. It gives good insight as to why certain features are to be avoided for performance, ie multiple inheritance, virtual functions under virtual inheritance, RTTI. The section on exception handling says that there are compiler dependent code size increases and speed is impacted (5% - 10%) even if it is not triggered. That contradicts Stroustrup in Design and Evolution of C++ where its stated that it should be the same cost as a function call. I've heard other people say that exception handling is now "free". I should spend less time gaining second hand information and more time trying this stuff out myself.