[racket] Queuing calls to printf

From: Danny Yoo (dyoo at hashcollision.org)
Date: Mon Oct 8 16:40:41 EDT 2012

> Since printf requires another thread to run, adding calls to printf in
> on-subwindow-event, or anything on-subwindow-event calls directly, will
> cause a GUI to break.

How about the logging functions such as log-debug?  Do they suffer
from the same problems?


Their output can be conditionally silenced by setting the system log
level appropriately (running with "racket ... -L debug", for example)

Posted on the users mailing list.