home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.scheme
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!sun-barr!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!bcm!rice!cs.rice.edu!dorai
- From: dorai@cs.rice.edu (Dorai Sitaram)
- Subject: Re: overwriting files?
- Message-ID: <Bx9MHE.6MM@rice.edu>
- Sender: news@rice.edu (News)
- Organization: Rice University, Houston
- References: <1da7u4INN43t@agate.berkeley.edu>
- Date: Thu, 5 Nov 1992 22:58:25 GMT
- Lines: 27
-
- In article <1da7u4INN43t@agate.berkeley.edu> bh@anarres.CS.Berkeley.EDU (Brian Harvey) writes:
- >R4RS doesn't seem to provide a standard way to open for writing a file
- >that already exists (to replace it with a new version).
- >
- >What do people do about this? Is there a portable solution? Is every
- >version of Scheme different about this?
-
- Imho, Scheme needs to allow _some_ way to test if a file
- exists and to delete a file. These need not actually be
- provided through new procedures file-exists? and
- delete-file. I think some dialects -- UMB Scheme? -- have
- open-input-file return #f (not error) on a nonexistent file
- and open-output-file destroy (if not exactly delete) an
- existent file. (Or maybe I'm thinking call-with-*-file.)
-
- Since we already have file procedures in r4rs, I don't think
- adding these testing and deleting capabilities can be
- subject to the same kind of controversy that might envelop
- "new" issues like macros, records, eval, etc. I'm curious
- that this area remains untouched in all the reports.
-
- --d
-
- --
-
- dorai@cs.rice.edu ! It may be that the gulfs will wash us down;
- dorai@owlnet.rice.edu ! it may be we shall touch the Happy Isles.
-