I know that generally, code and code explanations are not suitable for Software Engineering, but I thought this question, although it's phrased as asking for a code technique, really needed a rethink of the Software Engineering approach.
There is indeed a way to do that, but also likely a better way to approach the problem. I'll show both.
Add instrumentation
It's not always to tell when constructors and destructors are being called, so it's useful to add instrumentation. Here's some code I use sometimes that uses the Curiously...
There is indeed a way to do that, but also likely a better way to approach the problem. I'll show both.
Add instrumentation
It's not always to tell when constructors and destructors are being called, so it's useful to add instrumentation. Here's some code I use sometimes that uses the Curiously...
The Whiteboard
The Whiteboard