Object *objs;
objs = new Object[someint];
class Object
{
...
void Something()
{
if(whatever)
{
delete this;
}
}
};
Quote:Original post by CProgrammer
If I call delete this within all the dynamically allocated objects will all the memory be perfectly freed again?
// example 1MyObject *array = MyObject[1024];delete [] array;// example 2MyObject *array = MyObject[1024];for (unsigned int i = 0; i < 1024; i++)delete array + i;Quote:Original post by swiftcoderQuote:Original post by CProgrammer
If I call delete this within all the dynamically allocated objects will all the memory be perfectly freed again?
Yes, it really makes no diference, for instance, the following produce the same result:
*** Source Snippet Removed ***
And yes, I know c++ purists will complain about that pointer addition, having been recently flamed on the point, but really, is delete &array any better?<!–QUOTE–></td></tr></table></BLOCKQUOTE><!–/QUOTE–><!–ENDQUOTE–><br><br>Nonono!!! Don't EVER do that. Those two examples do NOT do the same thing. In fact, example two is not legal! You can never call delete on the individual elements of a dynamically allocated array and think that it will deallocate the elements individually. You will get undefined results (which will often cause a program crash, or worse, your program won't crash but it will be in an undeterminable state). The ONLY valid way to deallocate a dynamically allocated array in C++ is to call delete [] on the pointer to the first element of the array.
Object *objs = new Object[someint]; delete [] objs; for ( int i = 0; i < someint; i++ ) { delete &objs; }or for ( int i = 0; i < someint; i++ ) { objs.FunctionThatContainsDeleteThis(); } Object * apObjs[ someint ]; for ( int i = 0; i < someint; i++ ) { apObjs = new Object; } for ( int i = 0; i < someint; i++ ) { delete apObjs; }or for ( int i = 0; i < someint; i++ ) { apObjs->FunctionThatContainsDeleteThis(); } 
