News for hackers. Stuff that matters.
Re:Gonix – Unix tools written in Go by misframer on Friday May 08, 2015 @11:05PM (#9515317)
No problem. Also, please do not ignore errors. They're meant to be handled.
Re:Gonix – Unix tools written in Go by polegone on Friday May 08, 2015 @11:16PM (#9515347)
I'm working on that as well. I just fixed cat to crash and log on error, and I'll be fixing the other commands soon.

By the way, I'm wondering how I should go through the file line by line with a reader.

I think the most efficient way may be to scan byte by byte from the start (head) or the end (tail), and count until reaching n amount of newlines (or stop if at the end of the file), then print the bytes between the start/end and the nth newline.

How does this sound?

Re:Gonix – Unix tools written in Go by misframer on Friday May 08, 2015 @11:45PM (#9515412)
Good question. I'm not sure. You might want to seek to the end and move back. You probably shouldn't do it byte-by-byte directly from the file since that's very inefficient. As you can tell, this is already starting to get complicated! Maybe you could try mmaping the file so you could treat it as a []byte.
Re:Gonix – Unix tools written in Go by laumars on Saturday May 09, 2015 @07:59AM (#9516135)
Last year I was trying to write a Go routine that read a file backwards. I was amazed how unexpectedly difficult that proved to be.

In the end I settled for reading it from the start which worked 99.999% of the time and enabled me to finish the project to the tight deadline I had. But I've always meant to go back and "fix" that code at some point.

Re:Gonix – Unix tools written in Go by sridca on Saturday May 09, 2015 @12:49AM (#9515540)
> By the way, I'm wondering how I should go through the file line by line with a reader.

Take a look at my Go package that allows you to programmatically do 'tail -f' - https://github.com/activestate/tail