2011/12/16 Peter Bex :
>
> Also, the API docs work better when you try to search
> for something:
> http://api.call-cc.org/doc/srfi-18/current-time
>
Thanks! My fault.
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mail
* Christian Kellermann [111216 13:48]:
> * Sascha Ziemann [111216 13:45]:
> > The documentation for the thread-sleep! function in the srfi-18
> > documentation mentions a function called current-time. But that can
> > not be found:
> >
> > http://wiki.call-cc.org/search?text=&ident=current-time
Hi Sascha,
On Fri, 16 Dec 2011 13:43:01 +0100 Sascha Ziemann wrote:
> The documentation for the thread-sleep! function in the srfi-18
> documentation mentions a function called current-time. But that can
> not be found:
>
> http://wiki.call-cc.org/search?text=&ident=current-time
You probably nee
On Fri, Dec 16, 2011 at 01:43:01PM +0100, Sascha Ziemann wrote:
> The documentation for the thread-sleep! function in the srfi-18
> documentation mentions a function called current-time. But that can
> not be found:
>
> http://wiki.call-cc.org/search?text=&ident=current-time
What do you mean? I
* Sascha Ziemann [111216 13:45]:
> The documentation for the thread-sleep! function in the srfi-18
> documentation mentions a function called current-time. But that can
> not be found:
>
> http://wiki.call-cc.org/search?text=&ident=current-time
Thanks for spotting this!
You can replace the time
The documentation for the thread-sleep! function in the srfi-18
documentation mentions a function called current-time. But that can
not be found:
http://wiki.call-cc.org/search?text=&ident=current-time
___
Chicken-users mailing list
Chicken-users@nongnu
2011/12/16 Peter Bex :
>
> This could be done, but adding finalizers to them would cause quite a
> performance hit, and it wouldn't *really* fix anything. It would just
> sweep the problem deeper under the rug. For example, if you open a
> lot of files in a program that doesn't do any (or much) a
On Fri, Dec 16, 2011 at 11:39:56AM +0100, obscurolocon...@googlemail.com wrote:
> 2011/12/15 Peter Bex :
> I would say the GC must close the connection. How will you ever be
> able to close the socket in this case:
>
> (use tcp)
> (let ((p (tcp-connect "localhost" 25)))
> (if #f #f))
>
> All re
2011/12/15 Kon Lovett :
>
> So:
>
> (message-digest-chunk-converter (lambda (obj) (call-with-output-string
> (cut serialize obj <>
>
> should be enough.
serialize from s11n has its own limitations.
I tried to write an exception to a file in order to be able to analyze
it later. For th
2011/12/15 Peter Bex :
>>
>> Without explicitly closing the two ports, I got the same socket leaking.
>
> That's normal for any socket, even for regular tcp sockets. You have
> to close both ends before the underlying connection is closed.
> This also exactly what http-client is doing when you call
10 matches
Mail list logo
