Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!rice!leto.rice.edu!matthias
From: matthias@leto.rice.edu (Matthias Felleisen)
Newsgroups: comp.lang.scheme
Subject: Re: open-input-file [topics from hell, part 2]
Message-ID: <1991Apr23.020930.24833@rice.edu>
Date: 23 Apr 91 02:09:30 GMT
References: <9104220310.AA01226@luke.eecs.wsu.edu> <9104221752.AA00289@august>
Sender: news@rice.edu (News)
Organization: Rice University, Houston
Lines: 11

In article <9104221752.AA00289@august> Alan@lcs.mit.EDU (Alan Bawden) writes:
>   From: Roger Nelson - Grad Student <rnelson@eecs.wsu.edu>
>   What would be wrong with the open file functions simply returing an error
>   code rather than a port or #f in the event of an open error.
>As I said before, what's wrong with this is that people will write programs
>that forget to check the return value.  I've been there.  

I agree, but why not invoke ERROR or some CONTINUATION object and
provide a facility that intercepts such control actions  :-) ? 

-- Matthias