Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81122
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54C4A44F.2030902@gmail.com>
References: <54C4A44F.2030902@gmail.com>
Date: Sun, 25 Jan 2015 11:30:46 +0000
Message-ID: <CAPwsocGFH2oM+sRj=811g+s2pM10d=2Ehbw4GjBmzqjjt5pxcg@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Vote results for default ctors RFC
From: leight@gmail.com (Leigh)

On 25 January 2015 at 08:07, Stanislav Malyshev <smalyshev@gmail.com> wrote:
> I am a bit disappointed by the result, as I think it would be a good
> change, but I am much more disappointed by the fact that that 20 people
> voted against it and not even half of them - I would say maybe 1/5 of
> them - chose to participate in discussion even minimally and explain
> what is wrong with it in their opinion. I understand when everybody
> agrees there's no need of the flood of +1s, vote is enough, but
> disagreement by its nature is more diverse. I think not bothering to
> discuss and then just voting "no" with no explanation is not how the
> healthy RFC process should be working.
>

My points were already covered I believe. In hindsight I should have
added a "me too".

I think that "might refactor one day" is a pretty flimsy excuse for a
feature, and if you're going to refactor, that constructor will
probably need some parameters passing anyway, so you still have to do
the work. I'm in the camp that thinks if you call a method that
doesn't exist, you've done something wrong (I particularly hate __call
too).

Leigh.