I'm a new Go programmer but a grey beard (I started programming in the 1970's). I'm just spit-balling but the behavior you describe suggest to me a locale problem. For example, the Go program is likely emitting UTF-8 but your MS Windows console is likely expecting a different encoding (e.g., code page ). See https://stackoverflow.com/questions/12053168/how-to-properly-output-a-string-in-a-windows-console-with-go as one of many results I get when I search for "go println windows". See also https://en.wikipedia.org/wiki/Windows_code_page.
On Tue, Mar 12, 2019 at 7:20 PM rick <rapodr...@gmail.com> wrote: > I ran this same program: > https://www.thepolyglotdeveloper.com/2017/05/network-sockets-with-the-go-programming-language/ > : > > in Linux, and the output was exactly as expected. But on Windows, I was > seeing unexpected results. Sometimes just a newline printed. Sometimes the > entire buffer printed, but it was all whitespace. But it worked fine on > Linux. Any ideas? At first I thought it was related to the concurrency, but > the app never ended or broke connections unexpectedly, but then it worked > fine on Linux > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Kurtis Rader Caretaker of the exceptional canines Junior and Hank -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
