Posted by Sanders Kaufman on 07/23/07 13:09

Toby A Inkster wrote:
> Sanders Kaufman wrote:
>
>> So extended (child?) classes MUST NOT (for OOP reasons) automatically
>> call a constructor. Rather, it should be called manually, if and when
>> it's desired.
>
> s/MUST NOT/DO NOT/
>
> Of course, if you don't define a __construct() method in the child
> class, the parent class' constructor will get called automatically.
>
> Basically, in PHP __construct() behaves the same way other methods
> do: if you define the method in a child class, the parent class'
> method will be ignored, unless you explicitly call it from within
> the child class' method (using "parent::method()").

So to correct my statement:

In OOP (not just PHP) the constructor of the grandest child :) will be
called when a class is instantiated as an object.

Zat right?

Vocabulary question: When I do this, what is the OOP thing that I'm
doing? You said that my use of an object as a property of the parent
class was "aggregation. So - when I use use "extends" to create the
child's reference to the parent - wassat? Marshalling? Inheritance?

• Next in forum: Re: Are PHP libraries linked dynamically or statically?
• Prev in forum: Re: If you are looking for
• Thread view: Re: Using a Resource as a Class Property

[Reply to this message]