Currently, to represent a newline in go programs, I use \n
. For example:
package main
import "fmt"
func main() {
fmt.Printf("%d is %s \n", 'U', string(85))
}
... will yield 85 is U
followed by a newline.
However, this doesn't seem all that cross-platform. Looking at other languages, PHP represents this with a global constant ( PHP_EOL
). Is \n
the right way to represent newlines in a cross-platform specific manner in go / golang?
Having the OS determine what the newline character is happens in many contexts to be wrong. What you are really want to know is what the "record" seperator is and Go assumes that you as the programmer should know that.
Even if the binary runs on windows it may be consuming a file from a Unix OS.
Line endings are determined by what the source of the file or document said was a line ending not the OS the binary is running in.
I got curious about this so decided to see what exactly is done by
fmt.Println
. http://golang.org/src/pkg/fmt/print.goIf you scroll to the very bottom, you'll see an
if addnewline
where\n
is always used. I can't hardly speak for if this is the most "cross-platform" way of doing it, and go was originally tied to linux in the early days, but that's where it is for the std lib.I was originally going to suggest just using
fmt.Fprintln
and this might still be valid as if the current functionality isn't appropriate, a bug could be filed and then the code would simply need to be compiled with the latest Go toolchain.You can always use an OS specific file to declare certain constants. Just like
_test.go
files are only used when doinggo test
, the_[os].go
are only included when building to that target platform.Basically you'll need to add the following files:
You can declare a LineBreak constant in each of the
main_[os].go
files and have your logic inmain.go
.The contents of you files would look something like this:
main_darwin.go
main_linux.go
main_windows.go
and simply in your
main.go
file, write the code and refer toLineBreak
main.go