Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69430
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <004501cebafe$1f46b470$5dd41d50$@tutteli.ch>
References: <004501cebafe$1f46b470$5dd41d50$@tutteli.ch>
Date: Tue, 1 Oct 2013 12:17:45 +0200
Message-ID: <CAH-PCH7JwiCNLm_sp+t1WBQ=u+B4ehn4UPBFTDsAaSEBp+-ahA@mail.gmail.com>
To: Robert Stoll <rstoll@tutteli.ch>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0149d26e90c4c604e7ab43df
Subject: Re: [PHP-DEV] __construct is like a normal method but without E_STRICT
From: tyra3l@gmail.com (Ferenc Kovacs)

--089e0149d26e90c4c604e7ab43df
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 26, 2013 at 11:19 PM, Robert Stoll <rstoll@tutteli.ch> wrote:

> Heya
>
>
>
> I would like to have some opinions on the topic  inconsistency between
> methods and __construct
>
> See the following code:
>
>
>
> class A {
>
>                 function __construct($a) {}
>
>                 function foo($a) {}
>
> }
>
> class B extends A {
>
>                 function __construct($a, $b) {}
>
>                 function foo($a, $b) {}
>
> }
>
>
>
> If you work in strict mode, then you will see the error message
>
> Strict Standards: Declaration of B::foo() should be compatible with
> A::foo($a)
>
>
>
> I perfectly understand that the strict standard cannot be applied to the
> __construct and I would not suggest to change that. But I think it is
> somewhat strange that I am able to call __construct as it was a normal
> method from everywhere.
>
> Am I the only one thinking this, is there actually someone who is using
> __construct as re-initialising method?
>
>
>
> Cheers,
>
> Robert
>
>
>
>
>
>
>
>
php doesn't invoke the parent's constructor from the subclass if the
subclass also have a constructor, so in that case calling
parent::__construct() manually is your only option if you want the parent
constructor to be executed.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--089e0149d26e90c4c604e7ab43df--