Sepples Timer Issue

So I have this timer class implementation mostly done with extensive use of boost, bind, etc. It's logically structured as having a default container and containers are available as a type so you can include them with any classes. When the container dies, so do the timers in it. There's a specific timer thread in this application that does all timer operations.

After coding for 5 hours straight, I've no fucking clue what I'm doing and this is likely the last barrier to my code working masterfully.

I have a class that's implemented as a singleton that manages all the resources necessary to it. When I pass resources for it to handle, it works perfectly fine if I only pass resources once before the timer ends. However, if I queue up numerous resources to handle, the timer causes a heap error upon the first completion of the timer which is supposed to spawn another timer that does the same thing.

The only thing I can think of is that I'm doing pointer-to-member functions wrong, but god damn if I can figure out how to do it.

Any anons happen to have advice or questions about things I should be elaborating on? Thanks in advance.

>>3
son, I can assure you I know what I'm talking about. it seems to me like you fell into the trap of wanting to convolute your design with as many buzzwords as possible. I've seen it happen to countless grad kids, and I can see it's happened on you.

tell me, was it worth it? you're no segfaulting and leaking memory out the ass. you truly are pitiful.
post your code, so I can look at how foolish you are