OOP is great because in a number of ways it is more natural for english speakers, anyone who does math, and in some ways to any human:
1. Method and field calling matches english and math Subject/Verb/Object:
IMHO, OOP is best applied to creation of libraries, and mark should have left out the procedural methods and done most of the mods with just OO (yes, i know the procedural commands are ofte just wrappers for methods/fields). I know alot of the procedural people would hate this though, so mark has no choice. OO does apply well to SOME elements of a game/app. for instance, players, enemies, etc. However, you should use it restrictivly. For level data for instance, a type for each tile is crazy in most cases. just use an array. Also, dont make Types for things you only use once per loop.
Persanally, atm bmax's oop support isnt that great. No overloads, no private elements, no properties, no templates. (order of my opinion of need)
1. Method and field calling matches english and math Subject/Verb/Object:
Subject Verb Object(s) Bank PokeInt Index, Value <OOP Mark Add Overriding, Private Members, and Properties <English 2 + 2
It's not a problem with OO, it's a problem with people just going ahead and using it without really knowing how to use it well. Without getting some really good training on how to make good OO programs. I was from the hacker mentallity. Self taught, learned what I needed. And guess what. I've been doing C++ for about 7 years now and I don't consider myself a great OO designer. I just got the job done how I knew and I was not (Am still not) interested in being an OO design guru - that doesn't mean learning isn't a good thing of you want to be great at what you do. I'm just happy to not be great at it (Programming theory is too boring)
True, there are all those desing patterns, etc, and rampant misuse of OO.one oribkem is programmers rooted in a procedurall style will ask why they should use OOP. There is no concrete reason as far as functionality/speed goes that makes oop better. OOP can be implemented as a preprocessor on nearly any procedural language. C++ is a preprocessor for C.IMHO, OOP is best applied to creation of libraries, and mark should have left out the procedural methods and done most of the mods with just OO (yes, i know the procedural commands are ofte just wrappers for methods/fields). I know alot of the procedural people would hate this though, so mark has no choice. OO does apply well to SOME elements of a game/app. for instance, players, enemies, etc. However, you should use it restrictivly. For level data for instance, a type for each tile is crazy in most cases. just use an array. Also, dont make Types for things you only use once per loop.
Persanally, atm bmax's oop support isnt that great. No overloads, no private elements, no properties, no templates. (order of my opinion of need)