Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69358
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain tutteli.ch designates 80.74.154.78 as permitted sender)
To: <internals@lists.php.net>
Date: Thu, 26 Sep 2013 23:19:44 +0200
Message-ID: <004501cebafe$1f46b470$5dd41d50$@tutteli.ch>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0046_01CEBB0E.E2D291B0"
Thread-Index: Ac66/aGG94ZbPAPfRWOj4mnfKRHNDA==
Content-Language: de-ch
Subject: __construct is like a normal method but without E_STRICT
From: rstoll@tutteli.ch ("Robert Stoll")

------=_NextPart_000_0046_01CEBB0E.E2D291B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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

 

 

 


------=_NextPart_000_0046_01CEBB0E.E2D291B0--