From ...
From: Erik Naggum <cl@naggum.no>
Subject: Re: case sensitivity
Date: 1998/06/03
Message-ID: <3105885575342455@naggum.no>#1/1
X-Deja-AN: 359208760
References: <cxjyavmnwup.fsf@hawk.bu.edu> <6kvch0$bgb@news.u-bordeaux.fr> <sfwogwcff9k.fsf@world.std.com> <35746276.52BFA1D7@zeta-sqoft.com>
mail-copies-to: never
Organization: Naggum Software; +47 8800 8879; http://www.naggum.no
Newsgroups: comp.lang.lisp


* Scott L. Burson
| That's one way to put it.  One could also say that while INTERN is
| case-sensitive, READ is not (precisely because it translates).  From this
| perspective, the truth of "CL (as a whole) is case-sensitive" is not
| well-defined.

  I quite agree with Kent Pitman that CL is case-sensitive.  CL would be
  case-insensitive if INTERN ignored case.  the reader can ignore case or
  preserve it or do some perverse magic through READTABLE-CASE accessor on
  readtables.

  however, there is one place in the standard that puzzles me.  22.3.5.4
  Tilde Slash: Call Function (in 22.3 Formatted Output) reads:

All of the characters in name are treated as if they were upper case.

  I find this curious.  was editing instructions for this clause neglected
  when READTABLE-CASE was voted on?

#:Erik, who likes :INVERT
-- 
  "Where do you want to go to jail today?"
			-- U.S. Department of Justice Windows 98 slogan