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 function". I went digging through Wills and Plumbers > but I'm having trouble grokking it. Am I headed in the right direction, or > is there a better way?
Wills and plumbers will not help. Do you have control over where the port is used to that you can substitute another port? In that case, you could wrap the port with `make-input-port` or `make-output-port`, and then you have control over the close method. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/20200630164403.17c%40sirmail.smtp.cs.utah.edu.
