Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55500
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1109181708480.3630@whisky>
References: <CAKUjMCXiYc63NKsUuYWXT-A-aPabdPV6142LP9h4-c=2aUxW=w@mail.gmail.com>
	<4E74E5A0.2030006@sugarcrm.com>
	<alpine.DEB.2.02.1109181708480.3630@whisky>
Date: Sun, 18 Sep 2011 17:17:28 +0200
Message-ID: <CAEZPtU7x1iiDMKbc7oav+Rb4e4uaPrzzaAmjgjkEQ40X_SG08g@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, "RQuadling@GMail.com" <RQuadling@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] __constructor parameter limitations.
From: pierre.php@gmail.com (Pierre Joye)

On Sun, Sep 18, 2011 at 5:09 PM, Derick Rethans <derick@php.net> wrote:
> On Sat, 17 Sep 2011, Stas Malyshev wrote:
>
>> On 9/17/11 6:27 AM, Richard Quadling wrote:
>> > 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?
>>
>> I think the whole "strict parameters" thing has gone into somewhat wrong
>> direction and now we seem to have tons of useless errors and restrictions.
>
> If you don't want those warnings, turn them off! That's why there is a
> specific error level for it.

Well, that won't help for fatal error, which is what's this discussion
is all about, or almost :)


-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org