arborint wrote:Sure you are using the class construct, but essentially just namespacing your procedural function library with $_KERNEL.
I am reading C++, Primer Plus by Stephan Prata in order to get a different perspective on programming. From what I have read so far, I can see how you can view what I have done as "namespacing a procedural function library". I look at it from a different angle though.
Essentially, I look at classes as:
1. A module of code that performs a specific action.
2. Blocks of code that should function on their own with minimum dependencies.
3. A way to organize code.
4. A way to take a complex task and divide it into organized pieces by using methods.
5. A style of programming that allows me to reuse code in other applications.
arborint wrote:It is really not OOP at all.
OOP Stands for Object Oriented Programming. The second word, "Oriented" is ambiguous. How can I determine what the true definition of OOP is, when it contains ambiguity?
If 90% of my code uses classes, and if classes are considered objects, why is it not reasonable for one to conclude that it is "Object Oriented Programming"?