Found during pair programming (yes, I do it sometimes):<\/p>\n
... Yikes. Didn’t expect that to get by the compiler. But it did. Without even a warning. The compiler was happy to turn “new Foo” into a boolean value and instantiate f, silently letting the memory leak away.<\/p>\n This helps:<\/p>\n But still. Ug. Single argument constructors in C++ are just evil. <\/p>\n","protected":false},"excerpt":{"rendered":" Found during pair programming (yes, I do it sometimes): class Foo { public: Foo(bool in); … }; … Foo f = new Foo(true); … Yikes. Didn’t expect that to get by the compiler. But it did. Without even a warning. … Continue reading class Foo {
\n public:
\n Foo(bool in);
\n ...
\n };<\/p>\n
\n Foo f = new Foo(true);
\n ...<\/code><\/p>\n class Foo {
\n public:
\n explicit Foo(bool in);
\n ...
\n };<\/code><\/p>\n