At Wed, 7 Sep 2005 10:06:51 -0700, Kon Lovett wrote:
>
> The exception is raised in (read-block! ...): (u32vector-set! vec i
> (read-binary-uint32 port))
> (read-binary-uint32 ...) is returning a negative #, (u32vector-set!
> ...) only accepts positive #
The bug is in arithmetic-shift on 32-bi
At Thu, 15 Sep 2005 15:51:05 -0700, Kon Lovett wrote:
>
> In utf8.scm:
>
> (define string-hash (make-string-hasher byte-string-hash))
> (define string-hash-ci (make-string-hasher byte-string-hash-ci))
>
> And in byte-string.scm:
>
> (define byte-string-hash string-hash)
> (define byte-string-ha
Hi,
In the utf8.egg:
In utf8.scm:
(define string-hash (make-string-hasher byte-string-hash))
(define string-hash-ci (make-string-hasher byte-string-hash-ci))
And in byte-string.scm:
(define byte-string-hash string-hash)
(define byte-string-hash-ci string-hash-ci)
Where byte-string-hash is su
On Sep 15, 2005, at 6:19 AM, felix winkelmann wrote:
I'll take a look, thanks for reporting this.
cheers,
felix
This is actually fixed in the latest snapshot. Thanks!
- Mike Benfield
___
Chicken-users mailing list
Chicken-users@nongnu.org
http
On 9/15/05, felix winkelmann <[EMAIL PROTECTED]> wrote:
Hi, folks!The current snapshot that is available on the website (2.112) is broken.Please don't use it.
Thanks.
What is the latest usable snapshot?
Regards,
Nelson.-
___
Chicken-users mailing list
Date: Wed, 14 Sep 2005 18:11:45 -0400From: Michael Benfield <
[EMAIL PROTECTED]>Subject: [Chicken-users] tcp-connect doesn't correctly signal errorsTo: chicken-users@nongnu.orgMessage-ID: <
[EMAIL PROTECTED]>Content-Type: text/plain; charset=US-ASCII; format=flowed$ csi -q#;1> (require 'tcp)#;2> (
Hi, folks!
The current snapshot that is available on the website (2.112) is broken.
Please don't use it.
My apologies for the current chaos - I made some attempts of
migrating my build environment to another machine and failed
miserably (or better, tried to rush it). I'm behind a firewall right
n
On 9/15/05, Michael Benfield <[EMAIL PROTECTED]> wrote:
> $ csi -q
> #;1> (require 'tcp)
> #;2> (define-values (i o) (tcp-connect "slashdot.org" 12345))
> #;3> (write 5 o)
> Broken pipe
> $
>
I'll take a look, thanks for reporting this.
cheers,
felix
__
On 9/14/05, Vikash K. Mansinghka <[EMAIL PROTECTED]> wrote:
> When I execute
>
> chicken-setup debug
>
> a 404 page (instead of an egg) is recovered; manually visiting
>
> http://www.call-with-current-continuation.org/eggs/debug.egg
>
> yields the same thing. Figured it was worth reporting, eve
- Original Message -
From: Michael Benfield <[EMAIL PROTECTED]>
Date: Thursday, September 15, 2005 7:23 am
Subject: Re: [Chicken-users] tcp-connect doesn't correctly signal errors
> Indeed. But in C, the connect function returns -1 on error, and so I
> know that the socket file descriptor
- Original Message -
From: Michael Benfield <[EMAIL PROTECTED]>
Date: Thursday, September 15, 2005 7:23 am
Subject: Re: [Chicken-users] tcp-connect doesn't correctly signal errors
> tcp-connect should signal an exception. As it does
> if, for example, I do this:
> (tcp-connect "fakeurltha
On Sep 15, 2005, at 4:05 AM, Peter. Bex wrote:
In newer languages there are exceptions:
I appreciate the explanation but I assure you I am very familiar with
exceptions. My concern is only that tcp-connect silently gives me a
corrupt result rather than letting me know there was an error (thr
12 matches
Mail list logo
