"https://godoc.org/log#SetOutput": "SetOutput sets the output destination for the standard logger."
To me, without clarification, I assumed it would be globally re-directable at multiple times if desired, but it is only globally effective when ran early from main. I don't understand why it is designed this way? If you want package level log re-direction. I would have thought customisation, a flag switch or multiple processes communicating would make more sense than the current stdlib design. Is a log.SetGlobalOutput addition possible? Rather than people forking stdlib log...! https://stackoverflow.com/questions/29538668/logging-globally-across-packages p.s. I currently disagree with errors being an equivocal replacement for log redirection, as I have seen argued in past threads. p.p.s. I like err != nil Regards, Kc -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/fe7aa132-2275-24e3-f2e9-5048ef1987a3%40gmail.com.
