Note: This answer applies to C++03, and it seems like the behavior was changed in C++11 and higher so that this is now undefined behavior. It turns out that in this particular case the code is legal, but you’re ε-away from undefined behavior. The C++03 standard defines the notion of the “lifetime” of an object … Read more
If you use Process.Start you can pass in the Del parameter and the path to the application you wish to delete. ProcessStartInfo Info=new ProcessStartInfo(); Info.Arguments=”/C choice /C Y /N /D Y /T 3 & Del “+ Application.ExecutablePath; Info.WindowStyle=ProcessWindowStyle.Hidden; Info.CreateNoWindow=true; Info.FileName=”cmd.exe”; Process.Start(Info); Code snippet taken from this article
This way makes your program non OS dependant. from os import remove from sys import argv remove(argv[0]) Bonus points: When parsing arguments the very first argument that you get in sys.argv is equals to “path-to-filename/filename.py“
delete this is legal and does what you would expect: it calls your class’s destructor and free the underlying memory. After delete this returns, your this pointer value does not change, so it is now a dangling pointer that should not be dereferenced. That includes implicit dereferencing using the class’s member variables. It is usually … Read more
The C++ FAQ Lite has a entry specifically for this https://isocpp.org/wiki/faq/freestore-mgmt#delete-this I think this quote sums it up nicely As long as you’re careful, it’s OK for an object to commit suicide (delete this).