Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!fas-news.harvard.edu!newspump.wustl.edu!news.ecn.bgu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!pipex!dircon!rheged!simon
From: simon@rheged.dircon.co.uk (Simon Brooke)
Subject: Re: Upper/Lower Case Question
Message-ID: <D7CnI6.3ro@rheged.dircon.co.uk>
Organization: none. Disorganization: total.
References: <Pine.SUN.3.91.950414125759.27651A-100000@panix.com> <19950414T181207Z.enag@naggum.no>
Date: Thu, 20 Apr 1995 19:58:53 GMT
Lines: 36

In article <19950414T181207Z.enag@naggum.no>,
Erik Naggum  <erik@naggum.no> wrote:
>the :invert readtable-case is possibly more interesting:
>
>    CMU Common Lisp 17f, running on naggum.no
>    * (setf (readtable-case *readtable*) :invert)
>    :invert
>    * (defvar x 'z)
>    x
>    * (defvar y 'Z)
>    y
>    * (list x y)
>    (z Z)
>    * (equal x y)
>    nil
>    * (setf (readtable-case *readtable*) :upcase)
>    :UPCASE
>    * (list x y)
>    (Z |z|)
>    * (quit)
>
>if you use longer than one-character symbol names, this will work a little
>more intuitively than in the above example.  :)
>

H'mmm ... this is a trick I haven't seen before, and could make CL a
damn sight more tolerable (I *hate* a language which only knows how to
shout). Before I start madly into it, what are the disadvantages and
gotchas of using this as a standard working mode?



-- 
------- simon@rheged.dircon.co.uk (Simon Brooke)

			-- mens vacua in medio vacuo --
