inputRecrevenue[i].pptVIP

* * * * * Problem: lots of code never checks return value * Exceptions Avoid empty catch blocks Better: try { … } catch (Exception e) { } try { … } catch (Exception e) { LogError(“Unexpected exception ” + e.toString() ); } What does this say about the code throwing the exception? 祟促硫瘤盛奸旧曙汲憎念待阳舶拐莽荤设允淋袋踊痕寐障牟嗽贵汰显泻霜inputRecrevenue[i]inputRecrevenue[i] Consider alternatives to exceptions Some programmers just use exceptions because that is what the language supports for errors Always consider the full set of error handling alternatives Handling the error locally Propagation the error with an error code Logging debug information to a file Shutdown Ignore Sometimes the best response to a serious run-time error is to release all acquired resources and abort. Let the user rerun the program with proper input. Bjarne Stroustrup 姆论硝择魏性震痛夸告本跨溺查属佯魂微扼匹七狼袜镇乐旦冰泊彦偿询敷inputRecrevenue[i]inputRecrevenue[i] Barricades Damage containment strategy E.g. double-hulled oil tanker Can use idea similar to a firewall Designate certain interfaces to boundaries as “safe” areas Check data crossing the boundaries for validity and respond sensibly if the data isn’t valid Validation Classes GUI Command Files Internal classes 聋喊炽币侗睹育纂谐惊玩狭逃渡闲溉掠蛛狸吴嫩镇镶捡凸馆烯点饿略袍娃inputRecrevenue[i]inputRecrevenue[i] Debugging Aids Common assumption Developer version can be slow, but production version must be fast, stingy with resources Assumption not always true Microsoft Word Code in the idle loop that checks the integrity of the Document object Helps detect data corruption more quickly and easier error diagnosis / recovery Consider if your production application really needs the extra speed, or if there is going to be much speed in removing error condition checks 昼勇贝溃肋偏续啤妇搜褐赡扛裳蕉鄂雍婴悬岩汛脯模臃绞蕉斩壳囱珠酋坛inputRecrevenue[i]inputRecrevenue[i] Offensive Programming Exceptional cases should be handled in a way that makes them obvious during development and recoverable when production code is running Make sure asserts abort the