Subject: Re: bug#6878: bool-vectors of length 0 signal error when aref/aset the 0th element

From: Andreas Schwab <[email-masked]>
Date: Wed, 18 Aug 2010 10:36:40 +0200

MON KEY <[email-masked]> writes:

> As with the the first bool-vector of length 29 the second bool-vector
> of length 0 should also have a value at element 0 that evaluates to
> `t'.  (Or, it should according to the manual):

There is no element 0 in a 0-length bool vector, just like there is no
element 29 in a 29-length bool vector.

> Obv. taking the 0th index of a vector or char-table also signals an
> args-out-of-range error however I belive this for slightly different
> reasons.

In which way are bool vectors different from other vectors?

Andreas.

-- 
Andreas Schwab, [email-masked]
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."