On Apr 06, 2007, at 18:21 UTC, Daniel Stenning wrote: > The only thing is that the object instance might or might not still > exist or be accessible for inspection, depending on where the > exception gets caught.
If we're still talking about what happens when the debugger breaks on exceptions, then you don't have to worry about it; the break happens before the exception is actually thrown. And if we're talking about the trick where you raise and immediately catch an exception just to get the call stack, then the same applies; you won't have backed out of the call stack at that point either. > How would one get the errant class instance if > - for example the exception got caught much further up level wise - > for example in the App.UnhandledException event ? Right, in that case it may well be too late. > I think it would be more useful for the stack array to be able to > also contain the object instance ID info. Yes, that'd be a nice enhancement, if it doesn't already. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
