[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug in guile?
From: |
David Kastrup |
Subject: |
Re: Bug in guile? |
Date: |
Wed, 29 Aug 2012 09:52:07 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) |
David Kastrup <address@hidden> writes:
> "address@hidden" <address@hidden> writes:
>
>> Hey all,
>>
>> Could someone well-versed in guile try running primitive-load-path on
>> the attached file with and without the last line commented. Without
>> the last line commented, on my machine, I get:
>>
>> guile> (primitive-load-path "/home/mikesol/pleasework.lyaux")
>>
>> Backtrace:
>> In standard input:
>> 1: 0* [primitive-load-path "/home/mikesol/pleasework.lyaux"]
>>
>> standard input:1:1: In procedure string->number in expression
>> (primitive-load-path "/home/mikesol/pleasework.lyaux"):
>> standard input:1:1: Value out of range: 461
>>
>> However, with the last line commented, everything works ok. This
>> seems like a bug in Guile, but I wanna make sure that my input doesn't
>> seem off before I report it to the list.
>>
>> Cheers,
>> MS
>>
>>
>> (define my-hash (make-hash-table 100))
>> (hashq-set! my-hash
>> ae7d8fe61e91281e447a9e8c354114387284e14a0b4f3af8f392e1c9a943bd837ffb863f0602af
>> 7.45493)
>
> Uh, you are aware _how_ one writes hexadecimal constants in Scheme?
> They start with #x. I am surprised you should get an error only on the
> last line.
>
> The lack of an error might be worth investigating _if_ it is
> reproducible.
And by the way: don't use hashq-set! on numbers: the result is
undefined. You need to use hashv-set! to have equal values reliably map
to the same hash bucket.
--
David Kastrup