Newsgroups: comp.object,comp.lang.eiffel,comp.lang.c++,comp.lang.beta,comp.lang.java,comp.lang.sather Path: news.daimi.aau.dk!news.uni-c.dk!newsfeed.sunet.se!news01.sunet.se!sunic!newsfeed.ACO.net!Austria.EU.net!EU.net!howland.reston.ans.net!math.ohio-state.edu!newsfeed.acns.nwu.edu!ftpbox!mothost!schbbs!news From: shang@corp.mot.com (David L. Shang) Subject: Re: What Should An Exception Handling Do? -- Clarification of rules Reply-To: shang@corp.mot.com Organization: MOTOROLA Date: Wed, 27 Mar 1996 13:37:41 GMT Message-ID: <1996Mar27.133741.18132@schbbs.mot.com> References: <31583400.4CF9@Salsa.WallData.com> Sender: news@schbbs.mot.com (SCHBBS News Account) Nntp-Posting-Host: 129.188.128.126 Lines: 23 Xref: news.daimi.aau.dk comp.object:53294 comp.lang.eiffel:22536 comp.lang.c++:175308 comp.lang.beta:10686 comp.lang.java:29033 comp.lang.sather:12366 In article <31583400.4CF9@Salsa.WallData.com> Jerry Houston writes: > > I agree with the comments you made (and I snipped out), but one point > you didn't make in your reply was the location where execution resumes. > In the earlier quotation from ARM, "...from the throw point..." is the > operative phrase. I think there might be people here who otherwise > would be agreeing with each other, that are instead arguing. > > Resumption from the original invocation of a set of code that might > throw an exception (from the try{} block) is considerably different from > resumption from the point at which the error was detected. I have used > a method such as you described for so long, and with such complete > success, that I can't imagine anyone's finding fault with it. > Thanks for your supplementation. Yes, resumption should be done from the from the original invocation, not from the the throw point. If we find that our way will not lead to success, we cannot continue in the same direction from the point we find the problem. Resumption is a retry, and we must return the original point and go in a different way. David Shang