[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

*To*: common-lisp@sail.stanford.edu*Subject*: arrays*From*: Richard Berman <berman@vaxa.isi.edu>*Date*: Wed, 20 May 87 16:22:48 PDT*Posted-date*: Wed, 20 May 87 16:22:48 PDT

On bit vectors: on page 12: "One dimensional arrays of bits (that is, of integers whose values are 0 or 1) are called bit vectors" implies that any array of all 0 and 1 integers is a bit vector. Page 29: "All implementations are also required to provide specialized arrays of bits, that is, arrays of type (array bit); the one-dimensional instances of this specialization are called bit-vectors." Page 286: "Vectors whose elements are restricted to type bit are called bit-vectors" This implies strongly that a bit vector won't let one store any other value than 0 or 1. So, is this a bit vector? #(1 0 0 1) and should things like BIT-NOT which specifically want a bit vector work on it. Does it return a general vector like this in this case rather than something like *0110??? It is my *opinion* that #(1 0 0 1) is not a bit vector because there is a precise input style for such (like *1001) and bit vectors are specialized. What do you think? Is this a real maybe? RB

**Follow-Ups**:**arrays***From:*David A. Moon <Moon@STONY-BROOK.SCRC.Symbolics.COM>