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 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?
Ports are able to raise events. I don't know if any of these are directly useful to diagnose your early close problem, but you may be able to cobble something using multiple events.
https://docs.racket-lang.org/reference/sync.html https://docs.racket-lang.org/reference/port-lib.html?q=port#%28part._.Port_.Events%29 George -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/47967210-b87b-7a94-a9e2-035a8159e380%40comcast.net.
