J
jankeir
Guest
We have used your suggested approach with success: A companion OO object that keeps the state of the .p could also be an option, which gets its destructor called when the reference the .p has to it goes out of scope... It's not as clean as having a language construct build in off course but it does work reliably.
Continue reading...
Continue reading...