C++

1732 readers

1 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 2 years ago

MODERATORS

[email protected]

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

submitted 9 months ago by [email protected] to c/[email protected]

10 comments fedilink hide all child comments

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

[–] [email protected] 8 points 9 months ago* (last edited 9 months ago) (1 children)

I have worked with fairly large c++ codebases: It's totally possible to write much safer code than it ever was and I actually enjoy modern c++. Still it's still a burden and mishaps can and will happen. The time for the c++ committee to show they can overcome the language's issues has passed IMHO there are much better, and more expressive, alternatives.

I don't believe in the whole model of releasing a standard every 3 years and then taking who knows how long to implement it, and not braking compatibility. that shit just hinders the language. With all this said I don't think c++ is going to die any time soon.

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

The time for the c++ committee to show they can overcome the language’s issues has passed IMHO there are much better, and more expressive, alternatives.

I'm not sure if this is a good take.

Languages deemed "safe" boil down to two features: supporting specific memory management strategies, and adding static code analysis checks that enforce rules and best practices.

Can't this be done already without involving committees?

[–] [email protected] 3 points 9 months ago (1 children)

That works only if memory safety is optional. Additions of the language features needed for mandatory memory safety are backwards incompatible.