[racket] flush is not enough, a list is needed

From: Laurent (laurent.orseau at gmail.com)
Date: Mon Nov 5 03:16:58 EST 2012

Also, unrelated to the problem above, I want to close everything correctly
> when a problem occurs, but it seems that dynamic wind does not do that in
> case of a break (e.g., if the exn handler is removed, an invalid operation
> will raise an exception, but the ports will not be closed). I may be
> misunderstanding what dynamic-wind does.
> What would be the "right" way to do things here?

Ok... That's just because I used tcp-connect instead of
tcp-connect/enable-break, as well as tcp-accept counterpart. Now that works

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20121105/153e7679/attachment.html>

Posted on the users mailing list.