• @henfredemars@infosec.pub
      link
      fedilink
      English
      17
      edit-2
      1 month ago

      You can also make everything a smart pointer and be done with it.

      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.

      • @CanadaPlus@lemmy.sdf.org
        link
        fedilink
        11 month ago

        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.

        • @henfredemars@infosec.pub
          link
          fedilink
          English
          91 month 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.

        • @henfredemars@infosec.pub
          link
          fedilink
          English
          31 month 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.

    • qaz
      link
      fedilink
      English
      21 month ago

      const ref or unique_ptr if you need ownership