On 6/13/05, felix winkelmann <[EMAIL PROTECTED]> wrote:
>
> Ahem, no. Well it does, but it doesn't print the error message on retry.
> Give me a sec...
>
I forgot: you also need a new tcp.scm (attached).
BTW, is it somehow possible to nail down under what circumstances
the error occurs? (client
On 6/13/05, Peter Bex <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 13, 2005 at 10:07:35PM +0200, felix winkelmann wrote:
> > I have uploaded a new version of the http egg. tcp-accept should now be
> > retried
> > on failure and the error output shouldn't be as verbose as it is.
> > Perhaps you can try
On Mon, Jun 13, 2005 at 10:07:35PM +0200, felix winkelmann wrote:
> I have uploaded a new version of the http egg. tcp-accept should now be
> retried
> on failure and the error output shouldn't be as verbose as it is.
> Perhaps you can try it out?
Will do. Did you also think about providing a m
On 6/11/05, Peter Bex <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Spiffy just crashed on my machine. The error I got is pretty lame:
> thread thread2118 terminated with exception: can not write to socket: (18
> "HTTP/1.1")
> Error: (tcp-accept) could not accept from listener: #
>
I have uploaded
On 6/13/05, Michele Simionato <[EMAIL PROTECTED]> wrote:
> It looks like "handle-exception" cannot handles exceptions happening at macro
> expansion time:
>
> (define-macro (raise-error bool)
> (if (eq? #t bool)
> (error "error inside macro!"))
> #f)
>
> (handle-exceptions exn (print "e
It looks like "handle-exception" cannot handles exceptions happening at macro
expansion time:
(define-macro (raise-error bool)
(if (eq? #t bool)
(error "error inside macro!"))
#f)
(handle-exceptions exn (print "error caught")
(raise-error #t))
The error is NOT caught
On 6/11/05, Peter Bex <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Spiffy just crashed on my machine. The error I got is pretty lame:
> thread thread2118 terminated with exception: can not write to socket: (18
> "HTTP/1.1")
> Error: (tcp-accept) could not accept from listener: #
>
> Apparently for
