Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!rochester!pt.cs.cmu.edu!andrew.cmu.edu!bobg+
From: bobg+@andrew.cmu.edu (Robert Steven Glickstein)
Newsgroups: comp.lang.scheme
Subject: Re: Scheme Digest #125
Message-ID: <wYTTsRC00Vsn8KomQr@andrew.cmu.edu>
Date: 27 May 89 01:47:09 GMT
References: <8905250045.aa22349@mintaka.lcs.mit.edu>,
	<8905250927.AA29776@polya.Stanford.EDU>
Organization: Information Technology Center, Carnegie Mellon, Pittsburgh, PA
Lines: 14
In-Reply-To: <8905250927.AA29776@polya.Stanford.EDU>

> Excerpts from ext.nn.comp.lang.scheme: 25-May-89 Scheme Digest #125
> Jonathan Shapiro@POLYA.S (631)

> Very well.  I hereby specify an object whose name is

> 	#UNSPECIFIED

I second the motion.  I am currently designing ELSIE (the "Embedded Lisp
[Scheme] Interpreter, `ELSIE'"), and I'd rather not have to make
arbitrary decisions about what SET! returns (for instance).  (Actually,
set! is a bad example, since I believe it should return the new value,
which I guess I'm proposing for R4RS, but you get the idea.)

-Bob Glickstein