The second thing you tried is usually the best way to do this in Go: define an
interface with the methods that vary by type, and then make a function with the
type-independent logic. It’s actually cleaner in many cases than the classic OO
way with overriding methods, but a direct translation fro
Hi,
Where I work, we are currently experimenting with golang in order to
migrate our existing Perl codebase to golang.
Although Perl isn't a pure OO language, it allows for a lot of the OO
patterns to be used. One of the patterns we do use is where a superclass
method wraps a series of call to
