Re: [racket-users] Best way to ensure threads finish in GUI application?

Yep that's a typo. I've pushed a fix; thanks for reporting! https://github.com/racket/racket/commit/591d57b5bc11784b4d34860b26840ffe874bfb91 On Wed, Feb 22, 2017 at 10:36 PM, Vladimir Gajic wrote: > Is "(make-plumber) → pluber?" a typo in 14.11 Plumbers documentation?

Re: [racket-users] Best way to ensure threads finish in GUI application?

Is "(make-plumber) → pluber?" a typo in 14.11 Plumbers documentation? See https://docs.racket-lang.org/reference/plumbers.html?q=plumbers#%28def._%28%28quote._~23~25kernel%29._make-plumber%29%29 --Vlad On Tuesday, January 31, 2017 at 8:33:11 AM UTC-5, Matthew Flatt wrote: > I think you

Re: [racket-users] Detecting EOT when reading a TCP port

read-line returns eof when the port is closed, which is completely different from sending byte 04 (or any other byte or sequence of bytes) over the port. ;; set up {client,server}-{in,out} ports (write-byte 4 client-out) (flush-output client-out) (read-byte server-in) ;; => 4

Re: [racket-users] Best way to ensure threads finish in GUI application?

Is this a typo in the documentation: (make-plumber) → pluber? --Vlad On Tuesday, January 31, 2017 at 8:33:11 AM UTC-5, Matthew Flatt wrote: > I think you probably want `plumber-add-flush-handle!`: > > http://docs.racket-lang.org/reference/plumbers.html > > At Tue, 31 Jan 2017 13:23:03 +,

[racket-users] Detecting EOT when reading a TCP port

Hi all, Quick question: Given a listener and input port defined thus: (define listener (tcp-listen port)) (define-values (in out) (tcp-accept listener)) while reading lines of text, what’s the correct way to detect an EOT (^D or U+0004) character? This “obvious” solution does