From ...
From: Erik Naggum <erik@naggum.no>
Subject: Re: strings and characters
Date: 2000/03/18
Message-ID: <3162357232406441@naggum.no>#1/1
X-Deja-AN: 599089407
References: <ey3hfe73nm4.fsf@cley.com> <3162232362158363@naggum.no> <c_sA4.70$Hp4.1824@burlma1-snr2> <3162302923332864@naggum.no> <QPvA4.87$Hp4.2133@burlma1-snr2>
mail-copies-to: never
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: newsmaster@eunet.no
X-Trace: oslo-nntp.eunet.no 953371147 23439 195.0.192.66 (18 Mar 2000 09:19:07 GMT)
Organization: Naggum Software; vox: +47 8800 8879; fax: +47 8800 8601; http://www.naggum.no
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5
Mime-Version: 1.0
NNTP-Posting-Date: 18 Mar 2000 09:19:07 GMT
Newsgroups: comp.lang.lisp

* Barry Margolin <barmar@bbnplanet.com>
| I'm still not following you.  Are you saying that characters with
| implementation-defined attributes (e.g. bits or fonts) might not satisfy
| (typep c 'character)?

  no.  I'm saying that even as this _is_ the case, the standard does not
  require a string to be able to hold and return such a character intact.

#:Erik