I can count on more than one hand the number of large scale projects where converting everything to smart pointers fixed major memory issues. Even if smart pointers can’t handle circular references, the number of projects that just don’t manage their memory correctly at all and were fixed by introducing these tools is way too high.

[–] [email protected] 5 points 2 weeks ago (1 children)

This is a bit embarrassing but the last time I actively worked in C++ it was with Qt and pre C++11.

[–] [email protected] 3 points 2 weeks ago

Almost the same as me. All kinds of programming jobs. I usually end up working in Python or C, for embedded systems work.

Of course, if you’re talking hobby, it could be anything.

[–] [email protected] 1 points 2 weeks ago (1 children)

Which kind of smart pointer, with which kind of footgun? I mean, it's better than not even trying I guess, but if it was actually a full solution you'd just have Rust.

[–] [email protected] 9 points 2 weeks ago

You’re right. It’s a stop gap, but when you’re talking about a code base that has been maintained for 20 years plus you can’t really sell re-implementation.

Most recently it was with an older version of C++ using shared pointers.

[–] [email protected] 2 points 2 weeks ago

const ref or unique_ptr if you need ownership

[–] [email protected] 7 points 2 weeks ago (2 children)

I thought C++ was meant to get rid of C’s footguns?

[–] [email protected] 57 points 2 weeks ago (1 children)

It’s almost backwards compatible. You can use old or new foot guns.

[–] [email protected] 21 points 2 weeks ago

Hooray, choice!

[–] bitcrafter 22 points 2 weeks ago

C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off.

- Bjarne Stroustrup