There’s absolutely no authoritative definition of the expression “safe” in programming. Salesmen and advisers flex the term to match their demands. There is always the chance of safety being compromised in the case of software and programming. All it takes is a skilled hacker to gain entry into secure files. This is why monitoring has to be frequent, to secure vulnerabilities in a system before it is disclosed and penetrated.
A Safe Programming Language (SPL) guarantees that the application runtime (including the heap, heap or pointers or system code) can’t be subverted due to a programming mistake.
An SPL will ensure that a procedure will immediately terminate upon discovering this type of low-level mistake condition. The Cyber Attacker won’t have the ability to subvert the program runtime and “inject” his very own, malicious application code. The developer can then inspect the “remains” of the terminated process (for instance, a heart document) in a helpful way to examine and rectify the programming mistake.
Cases of Safe Programming Languages (in alphabetical order):
- SPARK Ada
- Visual Basic.Net
Examples of Unsafe Programming Languages (in alphabetical order):
- Ada, Assembly Language
What to do?
At any time you begin a brand new software development project, pick a more Safe Programming Language, rather than chosing the “industry standard” of unsafe languages such as C or C++. There exist high performance languages such as Cyclone, Modula-3 and Sappeur, which may compete with C/C++ concerning memory and processing time requirements.
Do not believe that you have been “among the few developers who will write bug-free code“.