this post was submitted on 17 Sep 2024
24 points (100.0% liked)

C++

12 readers
1 users here now

The center for all discussion and news regarding C++.

Rules

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] lysdexic@programming.dev 2 points 2 months ago (1 children)

The problem with C++ is it still allows a lot of unsafe ways of working with memory that previous projects used and people still use now.

Why do you think this is a problem? We have a tool that gives everyone the freedom to manage resources the way it suits their own needs. It even went as far as explicitly supporting garbage collectors right up to C++23. Some frameworks adopted and enforced their own memory management systems, such as Qt.

Tell me, exactly why do you think this is a problem?

[–] GetOffMyLan@programming.dev 12 points 2 months ago (1 children)

All the use after free and buffer overflow bugs that plague our key infrastructure.

[–] FizzyOrange@programming.dev 7 points 2 months ago (2 children)

It's not just that. Debugging segfaults and UB can be an absolute nightmare.

The C++ committee still haven't learnt their lesson. I recently learnt about C++20 coroutines, which are pretty neat, if complex (there are pretty much no good learning resources about them). However they are still putting unnecessary UB footguns in it.

[–] sukhmel@programming.dev 4 points 1 month ago (1 children)

Reminds me of how I found some safety measures to be in China some years back, basically those were signs saying "plz don't fall to your death, if you do it's your fault"

[–] lambalicious@lemmy.sdf.org 1 points 1 month ago (1 children)

At least it's not like Russia, where it's “plz don’t fall to your death, if you do it’s our fault”...

[–] sukhmel@programming.dev 2 points 1 month ago

I thought a lot of places are like that, that's why we get all the fences and such 🤔

[–] bufalo1973@lemmy.ml 1 points 1 week ago

Maybe a "pragma strict" where every deprecated is an error and not a warning?