To cope with errors in code we can do many thing, among many approaches the most powerful is to use “try catch finally” block around the code that might cause trouble (one we know that it throws Errors) but what I have noticed working with different programmers common mistake is to use “try catch” block as a filter of errors.
\n<\/p>\n
\r\ntry\r\n{\r\n willCauseTrouble();\r\n}\r\ncatch(e:*)\r\n{\r\n}\r\n<\/pre>\nThis is just asking for trouble we have no way to cope with that, if you did use the “try catch”, at least use it to report errors:<\/p>\n
\r\ntry\r\n{\r\n willCauseTrouble();\r\n}\r\ncatch(e:*)\r\n{\r\n trace("error occurred\\n"+(e as Error).getStackTrace());\r\n}\r\n<\/pre>\nnext thing is that instead of isolating the code that can cause trouble programmer wraps entire block of code within “try catch” statement.<\/p>\n
\r\n\/**\r\n * Dummy method to simulate error throwing\r\n *\/\r\nfunction problematicCode():void\r\n{\r\n throw new Error("Error");\r\n}\r\n\r\n\r\n\r\ntry\r\n{\r\n trace("action 1");\r\n problematicCode();\r\n trace("this action will not be executed")\r\n}\r\ncatch(e:*)\r\n{\r\n trace("I have caught an error");\r\n}\r\n<\/pre>\nabove snippet pictures this perfectly, the second trace is not executed, can you see my point, by wrapping entire block of code in the try we are stopping further execution, and it is a show-stopper. You should always try to predict which piece of code might be problematic, and “try catch” only it.<\/p>\n
\r\n\/\/-----------------\r\ntrace("action 1");\r\ntry\r\n{\r\n \/\/isolated problem\r\n problematicCode();\r\n}\r\ncatch(e:*)\r\n{\r\n trace("I have caught an error");\r\n}\r\ntrace("this action WILL BE executed")\r\n\r\n<\/pre>\nAnd as last word, this is debug utility not perfect hideout:) if your code throws errors, it can still work, but you should fix the cause, always.<\/p>\n
happy coding<\/p>\n","protected":false},"excerpt":{"rendered":"
To cope with errors in code we can do many thing, among many approaches the most powerful is to use “try catch finally” block around the code that might cause trouble (one we know that it throws Errors) but what … Continue reading