FAQ
io.Writer is not equivalent to a C "stream", whatever you meant by that.
The only way you get (write) buffering in Go is if you are working with a
bufio.Writer. C's standard library tends to buffer by default and you have
to turn it off or use syscalls directly to avoid it. Go's standard library
tends not to buffer by default and you need to wrap in bufio.* to get it.
And don't forget to Flush() or Close() your files if they are buffered!
On Wed, Aug 12, 2015 at 12:47 PM nicolas riesch wrote:

Aha moment:

In C, printf, fprintf functions write to a FILE *stream, and "stdout" is a
"stream", not a file.

In Go, fmt.Print, fmt.Fprintf functions write directly to a file, not a
Writer (equivalent to a C "stream").

It is just that the "stdout" word means different things in C and Go ...

Thank you for the explanation ;-)))

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 4 of 5 | next ›
Discussion Overview
groupgolang-nuts @
categoriesgo
postedAug 12, '15 at 5:21p
activeAug 12, '15 at 5:59p
posts5
users3
websitegolang.org

People

Translate

site design / logo © 2021 Grokbase