Object Oriented VS Procedural approach

[MJRomeo81]

I figured I would start a general thread discussing programming paradigms. While this isn't part of the VCAA course, I was wondering what the general consensus on this board seems to be. Has anyone coded with OO principles before?

[Lasercookie]

I've played around with it a bit before, but didn't venture too far into it (didn't get my head completely around concepts like inheritance, polymorphism etc. ) I think a lot of it went over my head, but it made a bit of sense when I tried coding a bit in it.

I think I indirectly dealt with it using Tkx for GUIs in Perl for ITSD. Widgets are objects etc. There's "object descriptions" listed as a design tool in the VCAA glossary. I assume the same for VB.Net. I know Python is fairly similar in that regard too.

For Perl at least, I didn't really go into the real concepts and approach you take for OO though (I guess the handy thing about most languages being multi-paradigm).

[paulsterio]

Although I've never really programmed a project big enough for object-oriented concepts to be of use, I've implemented things like inheritance and polymorphism before, when I was learning about object-oriented programming.

My view is that the bigger your project, the more you'll benefit from object-oriented programming purely because it encourages planning and structure over writing heaps of code without thinking about how it all relates.

[Yendall]

I've played around with it a bit before, but didn't venture too far into it (didn't get my head completely around concepts like inheritance, polymorphism etc. ) I think a lot of it went over my head, but it made a bit of sense when I tried coding a bit in it.

I think I indirectly dealt with it using Tkx for GUIs in Perl for ITSD. Widgets are objects etc. There's "object descriptions" listed as a design tool in the VCAA glossary. I assume the same for VB.Net. I know Python is fairly similar in that regard too.

For Perl at least, I didn't really go into the real concepts and approach you take for OO though (I guess the handy thing about most languages being multi-paradigm).

VB.net is object-oriented.

[paulsterio]

Most modern languages are object oriented, but it's really up to the programmer whether to see their programming as object-oriented and whether they use object-oriented styles.

[Yendall]

Most modern languages are object oriented, but it's really up to the programmer whether to see their programming as object-oriented and whether they use object-oriented styles.

Yeah this is true
What would be an example of an object-oriented style in VB?

[MJRomeo81]

• Creating and using classes and objects in VB.NET
• Encapsulation, Abstraction, Inheritance and Polymorphism.
• Constructors
• Overloading

To me, once you get your head around the concepts, the code looks a lot more cleaner particularly with inheritance (eliminating redundant code and extending the use of existing classes). Dealing with errors is a lot more pleasant too (exceptions to improve error handling - try/catch blocks).

[Yendall]

I base all my programming around objects really. I'm not familiar with the stages of OOP though, I should probably research into that more.