> But that assumes that the root cause of the error is where > the error was raised (or close to it). Often times it is > not (unless I stick in all my isinstance checks), so the > actual error entered the application state an hour ago, > the consequence just wasn't felt until later. But then in > a Smalltalk environment I suppose you could go manual > fiddle with the objects that have bad values.
It also assumes there is an exception. I often have errors in code (the kind that static typing captures) that don't manifest themselves as exceptions.
Previous Topic
