Re:Show HN: email - Send emails easily in Go
by scott_s on Tuesday January 07, 2014 @07:20PM
(#7020949)
Stuart Feldman, from "The Art of Unix Programming", on why makefiles must use tabs:
"Why the tab in column 1? Yacc was new, Lex was brand new. I hadn't tried either, so I figured this would be a good excuse to learn. After getting myself snarled up with my first stab at Lex, I just did something simple with the pattern newline-tab. It worked, it stayed. And then a few weeks later I had a user population of about a dozen, most of them friends, and I didn't want to screw up my embedded base. The rest, sadly, is history."
Re:Show HN: email - Send emails easily in Go
by DrJokepu on Tuesday January 07, 2014 @02:51PM
(#7019438)
If your package exports a single type only, New is more appropriate, if it exports multiple types, you should use NewObject:
Re:Show HN: email - Send emails easily in Go
by mseepgood on Tuesday January 07, 2014 @05:41PM
(#7020514)
Many packages have a dominant type and a couple of satellite types. If the package name is the same as or similar to the name of the dominant type, 'New' can be appropriate as well.
However, now that you mention it, I suppose it wouldn't have hurt, and the meaning would have been fairly clear. Oh well - live and learn, at this point, I'm doing my best not to break backwards compatibility if I don't have to.
Thanks for the heads up!
[1] http://golang.org/doc/effective_go.html#composite_literals
[2] https://sites.google.com/site/gopatterns/object-oriented/con...