Why should I not try to use “this” value after “delete this”?

by

The value of ‘this’ after calling delete is undefined, and the behaviour of anything you do with it is also undefined. While I would expect most compilers to do something sensible, there’s nothing (in the spec) stopping the compiler from deciding that its behaviour in this particular case will be emit code to format your hard-disk. Invoking undefined behaviour is (almost) always a mistake, even when your particular compiler behaves in the way you’d like it to.

You could work around this by taking a copy of the pointer (as an integer) before calling delete.

More Related Contents:

  1. What is the strict aliasing rule?
  2. C++ delete – It deletes my objects but I can still access the data?
  3. Has C++ standard changed with respect to the use of indeterminate values and undefined behavior in C++14?
  4. Why is unsigned integer overflow defined behavior but signed integer overflow isn’t?
  5. Do I need to cast to unsigned char before calling toupper(), tolower(), et al.?
  6. Is uninitialized local variable the fastest random number generator?
  7. May I treat a 2D array as a contiguous 1D array?
  8. Undefined behavior and sequence points reloaded
  9. Why do constant expressions have an exclusion for undefined behavior?
  10. How is a variable at the same address producing 2 different values? [duplicate]
  11. Why dereferencing a null pointer is undefined behaviour?
  12. C++ compilation bug?
  13. Is right shift undefined behavior if the count is larger than the width of the type?
  14. May I take the address of the one-past-the-end element of an array? [duplicate]
  15. Is this infinite recursion UB?
  16. Are memory leaks “undefined behavior” class problem in C++?
  17. Does not evaluating the expression to which sizeof is applied make it legal to dereference a null or invalid pointer inside sizeof in C++?
  18. Is reading an indeterminate value undefined behavior?
  19. In C++11, does `i += ++i + 1` exhibit undefined behavior?
  20. Why are arguments which do not match the conversion specifier in printf undefined behavior?
  21. Arithmetic right shift gives bogus result?
  22. Is pointer comparison undefined or unspecified behavior in C++?
  23. new() without delete() is Undefined Behavior or merely Memory Leak? [duplicate]
  24. Why does printf(“%f”,0); give undefined behavior?
  25. Near constant time rotate that does not violate the standards
  26. At what point does dereferencing the null pointer become undefined behavior?
  27. Undefined behavior causing time travel
  28. The behaviour of floating point division by zero
  29. Why doesn’t vector::clear remove elements from a vector?
  30. Setting extra bits in a bool makes it true and false at the same time

Leave a Comment