[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Scheme Digest #125

To: scheme@mc.lcs.mit.edu
Subject: Re: Scheme Digest #125
From: Robert Steven Glickstein <bobg+@andrew.cmu.edu>
Date: Fri ,26 May 89 21:47:09 EDT
Organization: Information Technology Center, Carnegie Mellon, Pittsburgh, PA
References: <8905250045.aa22349@mintaka.lcs.mit.edu>,
Sender: scheme-request@mc.lcs.mit.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

Follow-Ups:
- Scheme Digest #125
  - From: Morris Katz <mkatz@sesame.stanford.edu>

Prev by Date: semantics of DEFINE
Next by Date: XScheme and the whereabouts of David Betz
Previous by thread: Scheme Digest #125
Next by thread: Scheme Digest #125
Index(es):
- Date
- Thread