To PHP 5 and Beyond - Understanding OOP
Posted: Mon Jan 14, 2008 8:11 am
Note: If this is the wrong place to post this I'm sorry.
Guys,
Recently I've been reading a book by APress (Objects, Pattern and Design) and it's really opening my eyes on the benefits of PHP 5's new OOP model. I can't help but think that maybe PHP 5 still has room to grow. With that being said, I wonder just how much PHP 6 will really impact and matter when/if it is released in the future. I'm really afraid of PHP 6 being released just for the sake of releasing a new version basically.
Anyways, the true menaing of this post is a series of serious questions that I'm still unsure about (mainly because I haven't reached it in the book, so the anticipation is getting to me quicker than I can read). My concerns are with the advantages of cloning classes, Abstract classes, overloading classes, and interfaces. What are the true benefits of such things in OOP? Why would I use them, and better yet, where would be ideal usages for them?
The reason I ask is 2 fold: I'm coming from the PHP 4 age where we didn't have a true OOP so we designed around that fact, making classes just for reuse and not so much for true OOP. How is using true OOP going to benefit the developer who comes in with this mentality? Why would we use the above methods if we already know how to get by without them. It just feels like they are avaiable to satisfy true OOP design, but how does it really help with speed and reusability?
Is this somehting I'm just going to have to learn and understand on my own?
Thanks.
Guys,
Recently I've been reading a book by APress (Objects, Pattern and Design) and it's really opening my eyes on the benefits of PHP 5's new OOP model. I can't help but think that maybe PHP 5 still has room to grow. With that being said, I wonder just how much PHP 6 will really impact and matter when/if it is released in the future. I'm really afraid of PHP 6 being released just for the sake of releasing a new version basically.
Anyways, the true menaing of this post is a series of serious questions that I'm still unsure about (mainly because I haven't reached it in the book, so the anticipation is getting to me quicker than I can read). My concerns are with the advantages of cloning classes, Abstract classes, overloading classes, and interfaces. What are the true benefits of such things in OOP? Why would I use them, and better yet, where would be ideal usages for them?
The reason I ask is 2 fold: I'm coming from the PHP 4 age where we didn't have a true OOP so we designed around that fact, making classes just for reuse and not so much for true OOP. How is using true OOP going to benefit the developer who comes in with this mentality? Why would we use the above methods if we already know how to get by without them. It just feels like they are avaiable to satisfy true OOP design, but how does it really help with speed and reusability?
Is this somehting I'm just going to have to learn and understand on my own?
Thanks.