Here's a function that creates a thread that waits until a port is closed
and then prints a message:
(define (watch-for-port-close p)
(thread (lambda () (sync (port-closed-evt out)) (eprintf "port
closed\n"
For example:
(define out (open-output-string))
(watch-for-port-close out)
On 6/30/2020 4:27 PM, David Storrs wrote:
I have a port that (my current theory says) is being closed when it
shouldn't, but I'm having trouble isolating exactly where and when. I
thought maybe I could do something Rackety to say "as soon as this
port gets closed, run this function". I
At Tue, 30 Jun 2020 16:27:56 -0400, David Storrs wrote:
> I have a port that (my current theory says) is being closed when it
> shouldn't, but I'm having trouble isolating exactly where and when. I
> thought maybe I could do something Rackety to say "as soon as this port
> gets closed, run this
It doesn't look like will executor will do what you want, since it has to
do with garbage collection rather than port closing.
This could be overkill, but it's possible to construct a custom port (
https://docs.racket-lang.org/reference/customport.html). Is it possible to
construct a new port
I have a port that (my current theory says) is being closed when it
shouldn't, but I'm having trouble isolating exactly where and when. I
thought maybe I could do something Rackety to say "as soon as this port
gets closed, run this function". I went digging through Wills and Plumbers
but I'm
It should be fine to do both of those in the same directory.
Sam
On Tue, Jun 30, 2020 at 4:47 PM 'John Clements' via Racket Users
wrote:
>
> D’oh! Closing the loop on this one… it appears to me that this problem
> occurred after running a “make” (that is, a BC make) in a directory in which
>
D’oh! Closing the loop on this one… it appears to me that this problem
occurred after running a “make” (that is, a BC make) in a directory in which
I’d been running “make cs”). I just did it again, which is how I figured it
out. It’s a silly mistake on my part. It seems that running
Thank you very much for coming back and posting this resource! I will be
reading it carefully and I'm already sure there is a lot of useful content!
Much appreciated.
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this
The "free online resource" I alluded to earlier is up on my Web page now.
https://cs.uwaterloo.ca/~plragde/flaneries/LACI/
I call it a "flânerie", but it's a mini-textbook on logic and proof
assistants, using Racket to first construct a small proof assistant
(Proust), expanding it to handle
Hi,
If you haven't completed it yet...please do.
https://forms.gle/XeHdgv8R7o2VjBbF9
(announcement: https://blog.racket-lang.org/2020/06/racket-survey-2020.html
)
If you have colleagues or peers who use Racket, or have used Racket in the
past, but are no longer on the mailing list/IRC/Slack,
10 matches
Mail list logo
