Refactor #9

[otiai10]

[btc]

The error value*

[otiai10]

I'm really glad for your advise!
Because I'm yet on the way to use golang effectively. 😔
Do you mind telling me some documents for best practice of handling error in go.
I want to try that

[btc]

this is a start: http://golang.org/doc/effective_go.html#errors

[btc]

In Go, functions can return multiple values. Generally it's good to return errors to the caller like so:

fileName, err := generateTempFile()
if err != nil {
  // handle error
}
examine(filename) // proceed; no error

[otiai10]

@0xbtc Thanks so much! I'll tackle those problems in #12