On 10/9/07, Larry Garfield <larry@xxxxxxxxxxxxxxxx> wrote: > > On Tuesday 09 October 2007, Tony Marston wrote: > Here's a better reason to not bother learning PHP 4-style OOP. You have > less > than a year until running PHP 4 at all is considered an unsupported > security > risk. Don't waste your time, since PHP 5 OOP IS different, because > reference > handling changed drastically which means what is "fast and easy" in PHP 4 > OOP > and what is "fast and easy" in PHP 5 OOP is hugely different. which i mentioned early on in the conversation; we got sidetracked on the argument about encapsulation for a while. > > if you read that one chapter i recommended you will see; acquiring the > > > behavior of the parent is not always desirable. > > > > Then why inherit from the parent in the first place? Or why not create a > > method in the subclass which overrides the method in the superclass, > thus > > changing the behaviour to what you prefer? I certainly don't need > > interfaces to do that. > > Because I want to syntactically guarantee the existence of certain methods > so > that I can reliably call functionality on them. Call-and-pray is an > unreliable methodology. Yes, that is syntactic sugar. See above. > > Can we stop with the pissing contest now? ive been sitting w/ my opinion about php4 for a while now; what can i say; i had to get it out and hear the opinion of people on the list. if anything i have learned some things and gotten insight to viewpoints i didnt realize existed. i hope i have been able to contribute something to someone amidst all the arguing. -nathan
