Everything is seen as a bitstream<\/p>\n\n\n\n
const_cast<\/code> it away if the handle is exposed (bad idea)<\/li><\/ul>\n\n\n\nPerformance-first design choice<\/p>\n\n\n\n
- do not pay performance penalty for features not used
– static compilation and binding by default
– unchecked type declarations (see above)
<\/li> - static compilation: the compiler tries to know everything at compile time
<\/li> - static binding by default (cheapest)
– pay extra to use virtual methods (overriding)
– [38] default parameter values are statically bound and not stored in vtable (i.e. overridden child method’s default values are ignored and parent’s default values are used ONLY WHEN called through up-casts)
<\/li> - inline is at the mercy of the optimizer (which can choose to emit an object if decided inlining is counter-productive). Mechanism that forces a function pointer to exist (pointing the function, virtual functions creates the pointer in vtable)<\/li><\/ul>\n\n\n\n
Toolchain<\/p>\n\n\n\n
- preprocessor (parser & macros)<\/li>
- compiler (create object files per translation unit, which is .c file in C)
– access control (encapsulation) extends the old trick of emulating private<\/code> in C++ through macros by marking functions as static<\/code> (local within translation unit) in C.<\/li>- linker (combine object files and adjust the addresses)<\/li><\/ol>\n\n\n\n
Templates behaves like a combination of macros (copy-and-paste with parameters) except it’s spread across the toolchain like inline<\/a> optimizations:<\/p>\n\n\n\n- Code bloat (one copy per type combination)<\/li>
- Can only live in the header files (it’s a template, not realized code, so no object is emitted like a .cpp file)<\/li><\/ul>\n\n\n\n
Parsing (language design)<\/p>\n\n\n\n
- most vexing parse<\/strong> [Effective STL Item 6]: if something can be interpreted as a function declaration, it will be interpreted as a function declaration<\/li><\/ul>\n\n\n\n
Plain Old Data Types (C++ classes tried to emulate in their operator overloading behavior)<\/p>\n\n\n\n
- [15] allow
(a=b)=c<\/code> chaining by returning *this<\/code> for operator=<\/code><\/li>- [21] disallow rvalue assignment
(a+b)=c<\/code> by returning const <\/code>object<\/li><\/ul>\n\n\n\n<\/p>\n
<\/div>