Bug in parse-integer?

Hi,

I'm probably missing something, but the following


CL-USER 51 > (let ((string (make-array 5 :adjustable t
                                       :fill-pointer 0
                                       :element-type 'standard-char)))
               (vector-push-extend #\0 string)
               (parse-integer string))

Error: No integer present in "0" from 0 to 1, parse-integer expected one.
  1 (abort) Return to level 0.
  2 Return to top loop level 0.



seems like a bug to me. What am I missing?


Regards,

Arthur Lemmens

Re: Bug in parse-integer?

On Mon, 26 Apr 2004 11:12:27 +0200, Arthur Lemmens <alemmens@xs4all.nl> wrote:

>
> I'm probably missing something, but the following
>
>
> CL-USER 51 > (let ((string (make-array 5 :adjustable t
>                                        :fill-pointer 0
>                                        :element-type 'standard-char)))
>                (vector-push-extend #\0 string)
>                (parse-integer string))
>
> Error: No integer present in "0" from 0 to 1, parse-integer expected one.
>   1 (abort) Return to level 0.
>   2 Return to top loop level 0.
>
> seems like a bug to me. What am I missing?

No, it's a bug:

  <http://weitz.de/cl-interpol/#lispworks>

I think Xanalys will send you a patch if you're a registered customer.

Edi.

Re: Bug in parse-integer?

On 26 Apr 2004, at 11:12, Arthur Lemmens wrote:

> CL-USER 51 > (let ((string (make-array 5 :adjustable t
>                                       :fill-pointer 0
>                                       :element-type 'standard-char)))
>               (vector-push-extend #\0 string)
>               (parse-integer string))
>
> Error: No integer present in "0" from 0 to 1, parse-integer expected 
> one.
>  1 (abort) Return to level 0.
>  2 Return to top loop level 0.
>
>
>
> seems like a bug to me. What am I missing?

Works for me on LWM and I don't think I got a patch for that.

Sven