Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uwm.edu!uwvax!daffy!saavik.cs.wisc.edu!quale
From: quale@saavik.cs.wisc.edu (Douglas E. Quale)
Newsgroups: comp.lang.scheme
Subject: evaluating () should be an error
Message-ID: <1991Mar24.064144.4256@daffy.cs.wisc.edu>
Date: 24 Mar 91 06:41:44 GMT
Sender: news@daffy.cs.wisc.edu (The News)
Organization: University of Wisconsin -- Madison
Lines: 11

IMHO, an attempt to evaluate () should be required by the standard to signal
an error.  This would clean up a bit of lazy coding by forcing the use of '().

Although I know that some people don't mind having () overloaded, I'm glad
that the standard finally requires () and #f to be distinct.  Programmers who
want a crutch can always (define nil '()) if they want.

Are there any scheme implementations that signal an error on evaluating () ?

-- Doug Quale
quale@saavik.cs.wisc.edu