Is C++ now a "safe" language?
-
I was reading this article that said that we need to yank out C++ code from dangerous areas and rewrite them in Rust. One commenter mentioned that the newest C++ iteration fixes all the problems. Now I had "retired" back when auto_ptr was the hot new thing to take care of the deletion problem, and it seems that there are some new language features to fix the issues that auto_ptr introduced, and of course there is the whole new section of the language to give us the functional programming paradigm (I always like to use that word, LOL). That said, I suppose even with all the new features, it still is possible to blow one's foot off, something that Rust does not seem to allow oneself to do. https://techcrunch.com/2017/07/16/death-to-c/[^]
-
I was reading this article that said that we need to yank out C++ code from dangerous areas and rewrite them in Rust. One commenter mentioned that the newest C++ iteration fixes all the problems. Now I had "retired" back when auto_ptr was the hot new thing to take care of the deletion problem, and it seems that there are some new language features to fix the issues that auto_ptr introduced, and of course there is the whole new section of the language to give us the functional programming paradigm (I always like to use that word, LOL). That said, I suppose even with all the new features, it still is possible to blow one's foot off, something that Rust does not seem to allow oneself to do. https://techcrunch.com/2017/07/16/death-to-c/[^]
-
I was reading this article that said that we need to yank out C++ code from dangerous areas and rewrite them in Rust. One commenter mentioned that the newest C++ iteration fixes all the problems. Now I had "retired" back when auto_ptr was the hot new thing to take care of the deletion problem, and it seems that there are some new language features to fix the issues that auto_ptr introduced, and of course there is the whole new section of the language to give us the functional programming paradigm (I always like to use that word, LOL). That said, I suppose even with all the new features, it still is possible to blow one's foot off, something that Rust does not seem to allow oneself to do. https://techcrunch.com/2017/07/16/death-to-c/[^]
If you follow good practice when designing your C++ code then your code will be safe. See :[C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines)
I'd rather be phishing!
-
I was reading this article that said that we need to yank out C++ code from dangerous areas and rewrite them in Rust. One commenter mentioned that the newest C++ iteration fixes all the problems. Now I had "retired" back when auto_ptr was the hot new thing to take care of the deletion problem, and it seems that there are some new language features to fix the issues that auto_ptr introduced, and of course there is the whole new section of the language to give us the functional programming paradigm (I always like to use that word, LOL). That said, I suppose even with all the new features, it still is possible to blow one's foot off, something that Rust does not seem to allow oneself to do. https://techcrunch.com/2017/07/16/death-to-c/[^]
-
If you follow good practice when designing your C++ code then your code will be safe. See :[C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines)
I'd rather be phishing!
I mean seriously... what does Bjarne know!?
Jeremy Falcon
-
I was reading this article that said that we need to yank out C++ code from dangerous areas and rewrite them in Rust. One commenter mentioned that the newest C++ iteration fixes all the problems. Now I had "retired" back when auto_ptr was the hot new thing to take care of the deletion problem, and it seems that there are some new language features to fix the issues that auto_ptr introduced, and of course there is the whole new section of the language to give us the functional programming paradigm (I always like to use that word, LOL). That said, I suppose even with all the new features, it still is possible to blow one's foot off, something that Rust does not seem to allow oneself to do. https://techcrunch.com/2017/07/16/death-to-c/[^]
C++ is far from a safe language. Specially if you need to deal with many DLLs, maybe compiled by different C++ compilers. Most of the safety features of C++ are only safe in the context of a single binary or maybe different binaries built by the same compiler. In fact templates in general (used by all kinds of "safe pointers") suffer a lot of optimizations that may break across binaries. So, is it safe now? Well, it has much more safety features than in the past. But those are not 100% guaranteed in all scenarios and, well, you can ignore them at any time.
-
Modern C++ (C++11 and up) gives you ways to protect yourself, but it doesn't force you to use them. And even then, it just makes it harder, not impossible, to do stupid stuff. But that's true for any language.
-
I was reading this article that said that we need to yank out C++ code from dangerous areas and rewrite them in Rust. One commenter mentioned that the newest C++ iteration fixes all the problems. Now I had "retired" back when auto_ptr was the hot new thing to take care of the deletion problem, and it seems that there are some new language features to fix the issues that auto_ptr introduced, and of course there is the whole new section of the language to give us the functional programming paradigm (I always like to use that word, LOL). That said, I suppose even with all the new features, it still is possible to blow one's foot off, something that Rust does not seem to allow oneself to do. https://techcrunch.com/2017/07/16/death-to-c/[^]
Avoiding smart pointers and third party fancy stuff, should do the trick. And most of the critical applications runs on embedded systems, that have their own simplified, hardware specific compilers.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
-
I was reading this article that said that we need to yank out C++ code from dangerous areas and rewrite them in Rust. One commenter mentioned that the newest C++ iteration fixes all the problems. Now I had "retired" back when auto_ptr was the hot new thing to take care of the deletion problem, and it seems that there are some new language features to fix the issues that auto_ptr introduced, and of course there is the whole new section of the language to give us the functional programming paradigm (I always like to use that word, LOL). That said, I suppose even with all the new features, it still is possible to blow one's foot off, something that Rust does not seem to allow oneself to do. https://techcrunch.com/2017/07/16/death-to-c/[^]
-
And that's good. Otherwise the language would be slow and too restricted to be of any use.
You mean like managed languages? :-D
The difficult we do right away... ...the impossible takes slightly longer.
-
You mean like managed languages? :-D
The difficult we do right away... ...the impossible takes slightly longer.
Yes. The worst thing is that some people don't really know what they are doing anymore and turned ignorance into a matter of faith. I have seen guys who were unable to find a memory leak that forced the server to be reset every day. Instead of finding the leak, they insisted on not managing memory and tried to bat the garbage collector into submission. I perfer C++, because it let's you do what you want and therefore also leaves you with the responsibility. When something goes wrong, it's time to use your head and not to recite religious beliefs.
-
I was reading this article that said that we need to yank out C++ code from dangerous areas and rewrite them in Rust. One commenter mentioned that the newest C++ iteration fixes all the problems. Now I had "retired" back when auto_ptr was the hot new thing to take care of the deletion problem, and it seems that there are some new language features to fix the issues that auto_ptr introduced, and of course there is the whole new section of the language to give us the functional programming paradigm (I always like to use that word, LOL). That said, I suppose even with all the new features, it still is possible to blow one's foot off, something that Rust does not seem to allow oneself to do. https://techcrunch.com/2017/07/16/death-to-c/[^]
-
Yes. The worst thing is that some people don't really know what they are doing anymore and turned ignorance into a matter of faith. I have seen guys who were unable to find a memory leak that forced the server to be reset every day. Instead of finding the leak, they insisted on not managing memory and tried to bat the garbage collector into submission. I perfer C++, because it let's you do what you want and therefore also leaves you with the responsibility. When something goes wrong, it's time to use your head and not to recite religious beliefs.
Last project I worked on had 250 meg in the source control repository. The 'performance' problems I encountered were all due to poor design and architecture decisions. Not mine. Best I can suppose it that they were based on ignorance, fantasy and whim. And some of that isn't conjecture when people actually admitted that they did it wrong or did it just to try something new. I am very thankful that I didn't also need to track down memory leaks.
-
I was reading this article that said that we need to yank out C++ code from dangerous areas and rewrite them in Rust. One commenter mentioned that the newest C++ iteration fixes all the problems. Now I had "retired" back when auto_ptr was the hot new thing to take care of the deletion problem, and it seems that there are some new language features to fix the issues that auto_ptr introduced, and of course there is the whole new section of the language to give us the functional programming paradigm (I always like to use that word, LOL). That said, I suppose even with all the new features, it still is possible to blow one's foot off, something that Rust does not seem to allow oneself to do. https://techcrunch.com/2017/07/16/death-to-c/[^]
I like C and C#, but I never really cared for C++. However, I wish C# were more like C++ -- multi-paradigm and multiple-inheritance. In my opinion, they made C# too much like VB and not enough like C++. I don't actually do much that requires OOP, so I find C# forcing me to define a class rather irksome.
-
Yes. The worst thing is that some people don't really know what they are doing anymore and turned ignorance into a matter of faith. I have seen guys who were unable to find a memory leak that forced the server to be reset every day. Instead of finding the leak, they insisted on not managing memory and tried to bat the garbage collector into submission. I perfer C++, because it let's you do what you want and therefore also leaves you with the responsibility. When something goes wrong, it's time to use your head and not to recite religious beliefs.
