Programming

17313 readers

90 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

145

C++ creator rebuts White House warning (www.infoworld.com)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/programming

104 comments fedilink hide all child comments

Python is memory safe? Can't you access/address memory with C bindings?

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

[–] [email protected] 12 points 7 months ago* (last edited 7 months ago) (1 children)

TLDR: But-hurt C++ dev has a hard time accepting that his favorite language is not memory safe.

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

C++ is leagues above C in this regard. He's rightly upset that they're lumping the two together.

Bjarne's work for safety profiles could indeed manifest in a solution that guarantees memory safety; time will tell. C++ is a moving target.

[–] [email protected] 13 points 7 months ago (1 children)

C++ is leagues above C in this regard.

It's really not. It has the same flaws, some libraries that promise to avoid them (as long as you don't hold them wrong - what every single programmer does), and lots and lots of new flaws that may come from anywhere.

[–] [email protected] 3 points 7 months ago

I use C, C++ and Rust in my dayjob.

I don't like C++, but I disagree with your statement.

C++ has:

a string type, which sidesteps error prone buffer juggling.
smart pointers for scope based deallocation.
generic data types. No more hand rolling list and mapping types with void *.

It's obviously still not a fully memory safe language, but it has some perks over C. I'd still much rather be using rust (most of the time).

[–] hunger 9 points 7 months ago* (last edited 7 months ago)

That depends on how you decide which bucket something gets thrown into.

The C++ community values things like the RAII and other features that developers can use to prevent classes of bugs. When that is you yard-stick, then C and C++ are not in one bucket.

These papers are about memory safety guarantees and not much else. C and C++ are firmly in the same bucket according to this metric. So they get grouped together in these papers.