Newsgroups: comp.lang.scheme
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!uhog.mit.edu!bloom-beacon.mit.edu!apollo.hp.com!netnews
From: sommerfeld@apollo.hp.com (Bill Sommerfeld)
Subject: Re: Use of 'else'
Sender: usenet@apollo.hp.com (Usenet News)
Message-ID: <D5tA8z.CEn@apollo.hp.com>
Date: Tue, 21 Mar 1995 22:24:35 GMT
References: <3kda86$1r1@canyon.sr.hp.com> <3kkjei$jcg@camelot.ccs.neu.edu>
Nntp-Posting-Host: snarfblatt.ch.apollo.hp.com
Organization: Hewlett Packard, Chelmsford Site
Lines: 18

This is a bit of a stretch, but..

There's one other advantage of a special-cased `else' over `#t' in
COND expressions: compile-time error checking.

If you have an `else' in any position other than the last, you'll get
an error.

if you have a #t in any position other than the last, you'll never
execute the cases after the #t.

A compiler could issue a warning for a #t (or any expression always
evaluating to #t) in any position other than the last in a COND..

I don't think it's a particularly likely error, but I can see it
happening if you delete one too many close parens by mistake..

						- Bill
