home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!doc.ic.ac.uk!uknet!mucs!m1!bevan
- From: bevan@cs.man.ac.uk (Stephen J Bevan)
- Newsgroups: comp.lang.scheme
- Subject: Re: overwriting files?
- Message-ID: <BEVAN.92Nov7134050@hippo.cs.man.ac.uk>
- Date: 7 Nov 92 13:40:50 GMT
- References: <1da7u4INN43t@agate.berkeley.edu> <Bx9MHE.6MM@rice.edu>
- Sender: news@cs.man.ac.uk
- Organization: Department of Computer Science, University of Manchester
- Lines: 17
- In-reply-to: dorai@cs.rice.edu's message of 5 Nov 92 22:58:25 GMT
-
- In article <Bx9MHE.6MM@rice.edu> dorai@cs.rice.edu (Dorai Sitaram) writes:
- Imho, Scheme needs to allow _some_ way to test if a file
- exists and to delete a file.
- [ some systems return #f when failing to open a file ]
- I'm curious that this area remains untouched in all the reports.
-
- I assumed (without any foundation) that the reason this area hadn't
- been touched upon was because one possible soulution involves
- "exception handling" whose status has yet to be decided upon. For
- example, if you try to open a file that doesn't exist should you
- return #f or call an "exception" (or just leave it undefined :-). If
- "exceptions" are to be used, ther are number of different styles
- ranging from DIY cheap and cheerful ones created with say
- macros+call/cc+set! to larger ones requiring additional primitives
- such as the Common Lisp and MIT Scheme condition systems.
-
- bevan
-