Raw, unchecked pointers and manual memory management facilitate unsafe code. Any language that supports these is potentially "unsafe" to some extent.
So why not simply eliminate these unsafe features? The answer is --- speed.
What makes C/C++ suspect with regard to safety is the fact that these languages tend to promote unsafe features and constructs as standard practice and offer no realistic alternative using their standard libraries.
It's possible to build/invent anything using these languages including safe practices --- but the end result will wind up looking foreign to most who normally use these languages and cost more than their employers normally expect to pay.
> Make sure to initialize newly allocated memory before it is read.
The FreePascal compiler would warn about the missing init (first example of the "The Heap and Use After Free" section).
That being said I think that uninitialized locals is really something from an other age. Modern languages should always default-initialize locals. Speed of execution is not an issue as optimizing-compilers are able to remove dead assignments.
Delphi does default initialize global variables and member variables of objects. It doesn't default initialize local variables (but it should for consistency).
Inline variable declaration with initialization makes it a bit nicer. You can write:
var myVar := 25;
To initialize myVar and type inference will make it an Integer. You can specify type if needed:
Raw, unchecked pointers and manual memory management facilitate unsafe code. Any language that supports these is potentially "unsafe" to some extent.
So why not simply eliminate these unsafe features? The answer is --- speed.
What makes C/C++ suspect with regard to safety is the fact that these languages tend to promote unsafe features and constructs as standard practice and offer no realistic alternative using their standard libraries.
It's possible to build/invent anything using these languages including safe practices --- but the end result will wind up looking foreign to most who normally use these languages and cost more than their employers normally expect to pay.
> Make sure to initialize newly allocated memory before it is read.
The FreePascal compiler would warn about the missing init (first example of the "The Heap and Use After Free" section).
That being said I think that uninitialized locals is really something from an other age. Modern languages should always default-initialize locals. Speed of execution is not an issue as optimizing-compilers are able to remove dead assignments.
Delphi does default initialize global variables and member variables of objects. It doesn't default initialize local variables (but it should for consistency).
Inline variable declaration with initialization makes it a bit nicer. You can write:
To initialize myVar and type inference will make it an Integer. You can specify type if needed: In their examples they say: But actually n2 is initialized to zero.And in the example freeing of objects, instead of using:
They should always use: That will free the object and set the object pointer to nil. Any subsequent attempt to access obj1 will result in an access violation.