Xref: utzoo comp.lang.scheme:1575 comp.lang.functional:404
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!chaph.usc.edu!usc.edu!news
From: news@usc.edu
Newsgroups: comp.lang.scheme,comp.lang.functional
Subject: Re: call/cc and referential transparency
Message-ID: <11665@chaph.usc.edu>
Date: 27 Aug 90 02:22:55 GMT
References: <1466@tub.UUCP> <418@ministry.cambridge.apple.com>
	<JINX.90Aug22120120@chamarti.ai.mit.edu> <583@array.UUCP>
	<1990Aug24.212055.8368@nixtdc.uucp>
Sender: news@chaph.usc.edu
Followup-To: comp.lang.scheme
Organization: University of Southern California, Los Angeles, CA
Lines: 8
Nntp-Posting-Host: girtab.usc.edu
In-reply-to: doug@nixtdc.uucp's message of 24 Aug 90 21:20:55 GMT
Originator: news@girtab.usc.edu

Functional exception handling is equivalent to extending functions to
a universal domain.  The traditional way of doing this seems to be
returning a special 'null' return result, possibly with encoded
information on what the error was.

-- 
The news poster I'm using has a tendency to eat From: and Sender:
lines.  If you want to mail me any replies, I'm raulmill@usc.edu