Christophe Rhodes  <csr21@cam.ac.uk> wrote:
+---------------
| rpw3@rpw3.org (Rob Warnock) writes:
| > Oh, you mean the way CMUCL[1] does?  ;-}  ;-}
| > 	cmucl> (upgraded-array-element-type nil)
| > 	BIT
| > 	cmucl> 
| 
| Look a bit deeper.
| 
| cmucl> (upgraded-array-element-type nil)
| BIT
| cmucl> (type-of (make-array 0 :element-type nil))
| (SIMPLE-BASE-STRING 0)
| 
| I don't think that cmucl's behaviour on this issue is the result of
| deep consideration :-)
+---------------

Yeah, I noticed that just after hitting <SEND> on the previous reply.
(Oops.)

+---------------
| For what it's worth, I've been doing some exploratory programming on
| this issue, and the preliminary results indicate that it doesn't seem
| to be an intolerable burden for sbcl to support the letter of the
| standard.
+---------------

Interesting.  Hmmm...  How does it now respond to Erran's original
question? CMUCL-18e says:

	cmucl> (subtypep 'string '(vector character))
	T
	T
	cmucl> 

Your new SBCL says...?


-Rob

-----
Rob Warnock, PP-ASEL-IA		<rpw3@rpw3.org>
627 26th Avenue			<URL:http://rpw3.org/>
San Mateo, CA 94403		(650)572-2607