Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!hookup!news.kei.com!sol.ctr.columbia.edu!news.ess.harris.com!jabba.ess.harris.com!Titan!mac
From: mac@Titan.ESS.Harris.com (Mike McDonald)
Subject: Re: Common Lisp' dual name space
Message-ID: <CyJH27.77A@jabba.ess.harris.com>
Sender: mac@Titan (Mike McDonald)
Nntp-Posting-Host: titan.ess.harris.com
Organization: Harris Information Systems Division
References: <19941029T053722Z.enag@naggum.no> <a6Byuc1w165w@sytex.com> <38u0n4$9qb@tools.near.net> <391dts$onj@uqcspe.cs.uq.oz.au> <19941031T111542Z.enag@naggum.no>
Date: Mon, 31 Oct 1994 13:20:30 GMT
Lines: 17

In article <19941031T111542Z.enag@naggum.no>, Erik Naggum <erik@naggum.no> writes:
|> [Anthony Berglas]
|> 
|> |   Given that the lisp community is dying, the last thing that is required
|> |   is it to be split for trivial reasons like this.
|> 
|> it's dying?  really?  well, some claim the planet is dying, too, and
|> methinks it's going to hang round for another few billion years.  adjusted
|> for scale, the same seems to apply to LISP.  those who care for the planet
|> thinks it will help if we clean it up.  LISP has been cleaned up a lot with
|> ANSI Common LISP.

  And really mucked up soem things. Try feeding (character 1) to your ANSI Common
Lisp and see what it spits back at you. (Answer: #\<some binary data representing
Control-A>). Yuch!!

  Mike McDonald		mac@trantor.ess.harris.com
