Bug in SUBSEQ when accessing simple bit vectors
"xenophonf" <[email protected]>
| Newsgroups | gmane.lisp.corman |
|---|---|
| Message-ID | <[email protected]> |
SUBSEQ doesn't return the proper values when operating on simple bit vectors. For example, Corman Lisp 2.01: ? (subseq (copy-seq #8*01101001) 0 4) #*0000 Whereas in Clisp 2.29 (on Mac OS X 10.2.4): [1]> (subseq (copy-seq #8*01101001) 0 4) #*0110 And in CMUCL 18d (on Red Hat Linux 8): * (subseq (copy-seq #8*01101001) 0 4) #*0110 -- Matthew X. Economou <[email protected]> - Unsafe at any clock speed! I'm proud of my Northern Tibetian heritage! (http://www.subgenius.com) "The reason that ed is the standard editor is to remind you that things could be worse, and once were." -- Tim Lavoie in comp.lang.lisp ------------------------ Yahoo! Groups Sponsor ---------------------~--> Get 128 Bit SSL Encryption! http://us.click.yahoo.com/xaxhjB/hdqFAA/xGHJAA/SyjtlB/TM ---------------------------------------------------------------------~-> To unsubscribe from this group, send an email to: [email protected] Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/