Hey, I read somewhere (I think I did) that the racket compiler backend is being rewritten to allow for other execution environments. a) is this true b) and if so what is the status c) and if b) true is there a chance to test this?
thanks for the link
is there a specific reason on why to reimplement Racket on top of Chez Scheme? Also the post doesn’t talk about compiler backends - or I have missed that. Another question - is this purely an experiment or is this suppossed to become Racket7?
I should have included the original message: https://groups.google.com/d/msg/racket-dev/2BV3ElyfF8Y/4RSd3XbECAAJ
The Racket backend itself is not being rewritten, since the idea is to replace it entirely with Chez Scheme in the near term. Longer term, we hope to be able to run Racket on other platforms/VMs/languages.
wow. double wow ++ this looks really promising. different racket langs running on a JVM or in the browser. extremely cool
If I have multiple threads, and I press Ctr+C, does anyone know which thread the signal is going to go to?
(The docs seem a little vague on this. Just saying that you register a thread with thread-break.)
Or maybe it’ll go to all of them (that are registered and have breaks currently enabled.)
Running some tests also seems to indicate the main thread.
Yes, Ctl+C sends a break to the main thread
Okay, thanks.
@mflatt In that case, is there any good way to have the signal be sent to another thread?
(About all I have at the moment is sending it through a channel or some shared state.)
The call-in-nested-thread function sets up a redirect, but otherwise the main thread has to specifically resend it
Mmm…okay. thanks.
Ya, as far as I can tell, call-in-nexted-thread is very similar to jus thread followed by a thread-wait
(kind of anyway.)
So ya, thanks.