Yet again, so true. I think I raised an FR a while back to allow all breaks to be replaced by a particular exception being raised in the final code. This is because , while I find breaks so useful for trapping errors ( both just in terms of typing and due to the debugging limitations of exception ) when it comes to final builds I need to go through the code replacing all breaks with a raiseException.
It would be nice if we could just specify a default exception to replace all breaks. I think to go along with this there is a need for more introspection features within RB so we can generate a very helpful "generic" error logging system, one which could - for example - OPTIONALLY - allow us to include not only the class/method causing the error but also the source line number. In addition a "class instance ID" would be useful - ie to optionally be able to make the app generate an unique ID for each instance of a class, that can be reported in error messages. I do this anyway in code and it is very useful for debugging, but it would be great to have RB do this automatically for a "debug" build. On 6/4/07 05:13, "Andy Dent" <[EMAIL PROTECTED]> wrote: > I agree, the number of times I've sat stupidly blinking at my code > when it has stopped at an exception, or break, .... > > This is one of those annoying situations where progressing further > into a good programming practice (robust code using exceptions to > handle situations) derails a very useful debugging tool. Regards, Dan _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
