Hi I start a thread printing a file. When the file will be very long (say 50 GB) the thread takes too much time and I kill it when it takes more time than I want to permit. Outside the thread I clean up. Closing the output-port before deleting the file takes much time. But to my surprise I can delete the file before closing the port, which hardly takes time. Nice. Is this intended behaviour? After deleting the file, the port remains open, but writing to it does nothing. Correct? Thanks, Jos 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/EEC04679-E526-4215-B4DE-502B5B10567A%40hxcore.ol. |
- [racket-users] Surprising but convenient Jacob Jozef
- Re: [racket-users] Surprising but convenient Sage Gerard
- Re: [racket-users] Surprising but convenient Bruce O'Neel
- RE: [racket-users] Surprising but convenient Jacob Jozef
- [racket-users] Re: Surprising but convenient George Neuner
- RE: [racket-users] Re: Surprising but convenient Jacob Jozef