Try stripping debug symbols. As to compile time, the pimpl pattern is your friend here.
Huh? Templates in C++ are pay-for-what-you-use; only those instantiations required by your code are generated. Note also the ability to extern templates added in C++0x, which allow you to collapse common instantiations…
Not sure what you mean with copy ctor bloat, but for your_flavor_of_smart_ptr, that's what the typedef keyword is for. A common idiom I use is to typedef a class's preferred smart-pointer as ptr_t within the class…
Really? C++ is perhaps the slowest moving language in my repertoire in terms of 'popular' approaches to solving common problems. Look how long a c++0x specification has taken. And also, www.boost.org. Don't code c++…
If only c++ had some sort of static type system which could be leveraged to provide compile-time checks... But seriously, this is a large part of the power of c++'s type system. Taking the article's example, if the…
Try stripping debug symbols. As to compile time, the pimpl pattern is your friend here.
Huh? Templates in C++ are pay-for-what-you-use; only those instantiations required by your code are generated. Note also the ability to extern templates added in C++0x, which allow you to collapse common instantiations…
Not sure what you mean with copy ctor bloat, but for your_flavor_of_smart_ptr, that's what the typedef keyword is for. A common idiom I use is to typedef a class's preferred smart-pointer as ptr_t within the class…
Really? C++ is perhaps the slowest moving language in my repertoire in terms of 'popular' approaches to solving common problems. Look how long a c++0x specification has taken. And also, www.boost.org. Don't code c++…
If only c++ had some sort of static type system which could be leveraged to provide compile-time checks... But seriously, this is a large part of the power of c++'s type system. Taking the article's example, if the…