On Sat, Oct 22, 2011 at 9:33 AM, Tony Garnock-Jones <[email protected]> wrote: > On 2011-10-22 11:14 AM, Jay McCarthy wrote: >> I don't think any change is necessary, because this can be done as a library: >> https://github.com/jeapostrophe/exp/blob/master/ethread.rkt > > I was hoping for something that works for threads created using (thread) > as well. Using either your approach or something like > https://gist.github.com/1306106 works well for programs where you > control all the threads, but I wonder about whether it composes well > with other code. Maybe it doesn't matter as much as I think, though.
Eh, I think imposing this on all the threads would be a bad idea because it would increase memory usage unexpectedly for a lot of programs, I would guess > > (Incidentally, there are deadlocks lurking in (update-thread!), but I > think those can be worked around. One way is via the gist above; another > is using the kill-safe single-write box I mentioned earlier today.) Ya, of course, but it's easy to fix. > > Regards, > Tony > -- Jay McCarthy <[email protected]> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
