[racket] plot-frame does not wait at end of process

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Mon Mar 11 16:53:51 EDT 2013

FWIW, the OP (of the linked thread) actually wanted multi-threading so,
IMO, it makes sense to make them actually explicitly ask for it in the


On Mon, Mar 11, 2013 at 3:51 PM, Eli Barzilay <eli at barzilay.org> wrote:

> A few minutes ago, Robby Findler wrote:
> > Michael Wilber kindly sent me the link:
> >
> >   http://lists.racket-lang.org/users/archive/2012-April/051485.html
> (Ah, sorry, I thought that you knew where the discussion was...)
> > and I think that this is not really a good argument for changing the
> > default behavior. A keyword argument that says "create a new
> > eventspace" seems okay, but the docs should explain that this is
> > multi-threading, and if you were to invoke methods of the plot frame
> > without first going to the new eventspace (via queue-callback or
> > something like that), then you'll probably get bad behavior.
> Sounds like exactly what I'm asking for: a sensible default that works
> naively, and if the new eventspace is really useful, then do that with
> a non-default keyword.
> --
>           ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
>                     http://barzilay.org/                   Maze is Life!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20130311/cfa34113/attachment-0001.html>

Posted on the users mailing list.