Hi morgon,
Now assume you have some code that someone else has written and where destructors run as above during gobal destruction and one of them (you are too lazy to figure out which) is doing something nasty. Would it be (as a hack of course) then possible to graft something on to ensure that the nasty thing is undone as the last thing that happens?
From my somewhat limited experience with it, fiddling with stuff during destruction is fraught with peril. I would argue that if someone else's destructor is doing something so complex/nasty in its DESTROY method that you have a need to undo what is being done there, it's that code that is to blame and that needs to be addressed.
What is this nasty thing you're trying to undo?
Regards,
-- Hauke D
In reply to Re^3: is there a way to ensure some code is the last thing that is run?
by haukex
in thread is there a way to ensure some code is the last thing that is run?
by morgon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |