I'm really not sure that oop is the ideal way of doing things. In some ways procedural was lacking but in some ways oop is lacking too. It's really a change in mindset (or paradigm) in thinking about things and structuring their relationships. It is pretty nice to modularize things and keep related things in the same place, but to do it strictly breaks down a number of more efficient ways of doing things. I don't want all my `objects` to be so separate that they barely talk to each other and have to do all kinds of formalities just to relay information back and forth. I am trying to design a game engine and make it sort of oop-ish to have objects and flexibility with them, so that it looks like each item is a separate entity, but separation is not a good foundation. The reality of the world is founded on separation ideas so maybe a separation-based paradigm is a good reflection of `life situations`, but at the same time I do not think this necessarily means that this solves problems in the most elegant or efficient way. The universe is just a big dream and who would want to use that for their inspiration when you have a clean and beautiful alternative? I prefer to look upon these paradigms and decide where i want to use oop and where i want to use procedural and where i want to put boundaries and when i want to follow rules and when i don't. That is more encompassing and inclusive and efficient to me.
Opinions on object oriented programming
BlitzMax Forums/BlitzMax Programming/Opinions on object oriented programmingThe forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.