Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!senator-bedfellow.mit.edu!dreaderd!not-for-mail
Sender: ca...@nerd-xing.mit.edu
Newsgroups: comp.lang.lisp
Subject: Re: Why learn Lisp
References: <pan.2002.08.25.07.02.46.793119.14463@charter.net> <3d69646c@news.sentex.net> <akbv5s$1hg2eu$1@ID-105510.news.dfncis.de> <bruce-C4F9D3.18254726082002@copper.ipg.tsnz.net> <akcr49$1huo3u$1@ID-105510.news.dfncis.de> <86lm6tubs9.fsf@gondolin.local.net> <akd460$1gdhbn$1@ID-105510.news.dfncis.de>
From: Dave Bakhash <ca...@alum.mit.edu>
Date: 26 Aug 2002 09:37:12 -0400
Message-ID: <c29fzx1bv1z.fsf@nerd-xing.mit.edu>
Organization: Massachusetts Institute of Technology
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 16
NNTP-Posting-Host: NERD-XING.MIT.EDU
X-Trace: 1030369032 senator-bedfellow.mit.edu 3928 18.7.16.74

"Adam Warner" <use...@consulting.net.nz> writes:

> I am aware that the read table can be set to case sensitive and the
> inplications for existing code and development environments breaking.

It seems that the underlying problem is that the symbols in the :cl
package are uppercased, which is why the default reader upcases symbols.

If you want case sensitivity, but still want to use lower-case, then use
:invert (and probably some implications on *print-case* as well, and
will cause problems when using existing code, etc.)

I don't do this, but I wonder if this (or something similar) is what
people who want a case-sensitive CL do.

dave