Dit bericht verscheen eerder bij FOSSlife
Significant safety changes appear to be forthcoming for the C++ programming language, according to the recent “Opinion on Safety for ISO C++” co-authored by Bjarne Stroustrup.
“Many have noted that safety-critical applications have proliferated even more than ever, putting more strain on programming languages to be safe,” the document says. “In reality, critical infrastructures have always required safety but there are now more of them and more demand for their safety aspect to be more evident.”
Nonetheless, “C++ appears, at least in public image, less competitive than other languages in regards to safety,” the document says.
The document also reviews the current state of C++ in regard to safety and outlines potential steps for moving forward:
We now support the idea that the changes for safety need to be not just in tooling, but visible in the language/compiler, and library. We believe it should be visible such that the Safe code section can be named (possibly using profiles), and can mix with normal code. Individual features may not be very visible, but will be more visible when packaged.
As David Cassel explains, “this new approach would ultimately bring not just safety but also flexibility, with profiles specifically designed to support embedded computing, performance-sensitive applications, or highly specific problem domains, like automotive, aerospace, avionics, nuclear, or medical applications.”
Lest these moves be viewed as hasty, the document specifically advocates a calm approach based on established tenets, which is “better than a reactive jump on the bandwagon.”
Read the complete document for more information.
Looking for a job?
Check out the latest job listings at Open Source JobHub and SysAdmin JobHub.
Dit bericht verscheen eerder bij FOSSlife
