> > In retrospect, thinking about the best way to find this kind of problem, > it seems some sort of 'object registry' where in the init of each class, > some code executes to 'register' it in a table/data structure of some > sorts(class, unique ID, and the call stack), and in the destroy it marks it > as 'destroyed'.
> Sorry, I should have pointed you to an article I recently released: > http://www.foxpert.com/docs/safeclasses.en.htm. Thanks. I'll have to check that out in more detail next time I need to find a problem like this. Thanks. -- Derek _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
