On Saturday, September 24, 2011 at 9:14:22 AM UTC-7, nvcnvn wrote: > > I just read here: > http://golang.org/doc/go_faq.html#Is_Go_an_object-oriented_language > And all of the GO example we have is not writen in OOP way. > So can I say that GO see the benefit of Procedural over OO!? >
Object oriented programming means different things to different languages. Depends on the examples you're looking at. For most example code in the standard docs, you're looking at a demonstration of an API. You instantiate a structure, and call a method or two on that structure. It doesn't "feel" object oriented, because you're talking about methods on a type (usually a structure) instead of a class. Once you start adding in interfaces when you need them, your perspective on the language may change considerably. > > For myself, I fell ok with Procedural programming! Just need to stay > come, do some document for your code and that will help me avoid > duplicate of code, or easy to maintain and modify my code. As with all things programming, best to learn a number of different paradigms, so you can apply the right one in the right context. Eric. -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
