C++

1718 readers

47 users here now

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

Rules

Respect instance rules.
Don't be a jerk.
Please keep all posts related to C++.

founded 1 year ago

MODERATORS

farados@vlemmy.net

Nihili0@programming.dev

lysdexic@programming.dev

The empire of C++ strikes back with Safe C++ blueprint (www.theregister.com)

submitted 2 days ago* (last edited 2 days ago) by cmeerw@programming.dev to c/cpp@programming.dev

33 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[+] lysdexic@programming.dev -6 points 2 days 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 13 points 2 days ago (1 children)

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

[–] FizzyOrange@programming.dev 6 points 2 days ago (1 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 2 points 1 day ago

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"