Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55476
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.215.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAKUjMCXiYc63NKsUuYWXT-A-aPabdPV6142LP9h4-c=2aUxW=w@mail.gmail.com>
References: <CAKUjMCXiYc63NKsUuYWXT-A-aPabdPV6142LP9h4-c=2aUxW=w@mail.gmail.com>
Date: Sat, 17 Sep 2011 15:43:26 +0200
Message-ID: <CAF+90c-YsWFtZVPajiUL6SKvde=EyVsSGAgWZrCCvT3Y9Q9YCw@mail.gmail.com>
To: RQuadling@gmail.com
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] __constructor parameter limitations.
From: nikita.ppv@googlemail.com (Nikita Popov)

Hi Richard!

Which change are you talking about? I just tried doing:
    <?php
    class A           { public function __construct($a)     { } }
    class B extends A { public function __construct($a, $b) { } }
And it worked on 5.4 Beta 1 without errors.

Nikita

On Sat, Sep 17, 2011 at 3:27 PM, Richard Quadling <rquadling@gmail.com> wrote:
> Hi.
>
> With the recent BC with regard the locking of the constructor's
> signature for subclasses, what is the expected mechanism for allowing
> a subclass to have additional parameters?
>
> You can always supply them and use func_get_args() / func_num_args() /
> etc. to read them.
>
> It would seem that the limitation restricts the capabilities. I'm not
> a purist. Software development is a compromise between purity and
> getting the job done in an efficient and understandable manner.
>
> By allowing undocumented parameters to the constructor (due to the
> enforced signature), this would seem to break things on a different
> front (I can't docblock non defined parameters for examples).