Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44653
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.206 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=iFMcw6FysJHQfdouxTfoCh6J65zj6ULY/+bL5KCnd3SEg0gNRN/zKVlMTXGwjS8ShQ
         TxLp068D6WsZQOYkKiJ3eVMd/8gHs8BVnCsDF2As31zwShRUkoS+BrvpKRAv+71NtNcK
         xowepXYeUC7ic8mzBSOwDeHUWMQdmssQmZ7k0=
MIME-Version: 1.0
Date: Thu, 2 Jul 2009 16:14:18 +0200
Message-ID: <98b8086f0907020714m6c67fce3jab4d13429b3cd2a4@mail.gmail.com>
To: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: constructors are callable as regular functions.
From: troelskn@gmail.com (troels knak-nielsen)

I just realised that the following is valid php code:

    class Foo {
      function __construct() {
        echo "constructor called\n";
      }
    }
    $f = new Foo();
    $f->__construct();

Output:

    constructor called
    constructor called

I would have expected the second call to __construct() to yield an error.

Has this been discussed before? In that case, was it decided to go
with this behaviour or is it purely accidental? Are there perhaps some
implementation issues in preventing the second call to __construct()?

--
troels