Path: news.daimi.aau.dk!news.uni-c.dk!newsfeed.sunet.se!news01.sunet.se!sunic!mn6.swip.net!plug.news.pipex.net!pipex!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!newsxfer2.itd.umich.edu!newsxfer.itd.umich.edu!ncar!newshost.lanl.gov!usenet
From: clodius@hotspec (William Clodius)
Newsgroups: comp.object,comp.lang.eiffel,comp.lang.c++,comp.lang.beta,comp.lang.java,comp.lang.sather
Subject: Re: What Should An Exception Handling Do? -- Clarification of rules
Date: 27 Mar 1996 08:45:34 -0700
Organization: Los Alamos National Laboratory
Lines: 12
Sender: clodius@hotspec
Message-ID: <g1enqeleu9.fsf@hotspec>
References: <Doq3sv.MzA@research.att.com>
	<1996Mar25.160011.13921@schbbs.mot.com> <4j954n$mrq@kai.com>
NNTP-Posting-Host: hotspec.lanl.gov
In-reply-to: robison@kai.com's message of 26 Mar 1996 10:14:15 -0600
X-Newsreader: Gnus v5.1
Xref: news.daimi.aau.dk comp.object:53397 comp.lang.eiffel:22569 comp.lang.c++:175608 comp.lang.beta:10692 comp.lang.java:29573 comp.lang.sather:12373

It should be noted that what David Shang was proposing was NOT
strictly speaking resumption semantics, where processing resumes
immediately after the point where the exception signal was generated,
but retry semantics, where processing resumes before the point where
the exception signal was generated.  Although I have not programmed in
it, Eiffel (and perhaps its relative Sather) allows retry semantics and
I am under the impression that it works well for some problems.

-- 
William B. Clodius		Phone: (505)-665-9370
Los Alamos National Laboratory	Email: wclodius@lanl.gov
Los Alamos, NM 87545