Thanks. I do use dynamic-wind in various ways now, but I'm not sure how it would help me in this particular scenario. My log receiver thread is simply in a loop sync'ing on the logger, so I can't wait for my thread. I don't know how to determine when all the log messages have been received. Sleeping for a second would probably do it, but that seems pretty kludgy :)
This is mainly a problem for logging in tests because they can finish so quickly. For my main application, I don't think it will be much of an issue. For my tests, I just created a wrapper that uses the default logger, and I'll control the amount of output with a PLTSTDERR env variable. On Friday, January 18, 2019 at 9:28:26 PM UTC-5, gneuner2 wrote: > > On Thu, 17 Jan 2019 18:08:00 -0800 (PST), Brian Adkins > <lojic...@gmail.com <javascript:>> wrote: > > >Aha! Thanks for the quick reply. I'll have to rethink how I'm handling > >logging. > > One thing you might try is to use dynamic-wind in your main thread, so > you can cleanly end loggin and shut down your logging thread even if > the main thread dies (or is killed). > > 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 racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
