Reply to post: Re: Unfair C++ bashing

Revealed: The 25 most dangerous software bug types – mem corruption, so hot right now

teknopaul

Re: Unfair C++ bashing

Rust seems good for this problem. It allows "unsafe" code to be wrapped with safe code interfaces. This way you can use tried and tested libs write the interface once (carefully reading the manual as you do so) and then forget about it from then on because the rust side of things is safe if it compiles.

Rust is not comparable to C++, its C-like with a whole bunch of problems moved to compile time.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon