From ...
From: Erik Naggum <erik@naggum.no>
Subject: Re: how to validate input?
Date: 2000/04/26
Message-ID: <3165777540956858@naggum.no>#1/1
X-Deja-AN: 616104547
References: <87wvlv75lf.fsf@inka.de> <u66t4rjy0.fsf@alum.mit.edu> <3165754243765645@naggum.no> <uln20pv0g.fsf@alum.mit.edu> <szJN4.2887$eD6.1398141@news-east.usenetserver.com>
mail-copies-to: never
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: newsmaster@eunet.no
X-Trace: oslo-nntp.eunet.no 956788992 5436 195.0.192.66 (26 Apr 2000 22:43:12 GMT)
Organization: Naggum Software; vox: +47 8800 8879; fax: +47 8800 8601; http://www.naggum.no
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5
Mime-Version: 1.0
NNTP-Posting-Date: 26 Apr 2000 22:43:12 GMT
Newsgroups: comp.lang.lisp

* kragen@dnaco.net (Kragen Sitaker)
| In the tail-call optimization case, I can't imagine why you'd want to
| give the user the option to turn off tail-call optimization if it were
| only a win for your particular implementation.

  consider full and accurate backtraces during debugging, profiling
  that reports correct call trees, and simply correct error messages.

  programmers prefer to be able to control optimization levels for a
  number of reasons.  Scheme doesn't have a standard way to express
  such preferences, either.  in other words, Scheme is not an option.
  (sorry, I had to.)

#:Erik