Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84845
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.179 as permitted sender)
Sender: Michael Wallner <mike.php.net@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F29A594F-C308-4AF5-AC41-4396DA7F3C9C"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
In-Reply-To: <CA+kxMuTh4haa=wF8h_gMp+cMocK3sG8sxwZnG=NHCORKi41TYQ@mail.gmail.com>
Date: Sun, 15 Mar 2015 17:17:45 +0100
Cc: "internals@lists.php.net" <internals@lists.php.net>
Message-ID: <AA73AA0C-7F83-46A4-AF35-B5E98BFCDB7C@php.net>
References: <CA+kxMuTh4haa=wF8h_gMp+cMocK3sG8sxwZnG=NHCORKi41TYQ@mail.gmail.com>
To: Dan Ackroyd <danack@basereality.com>
Subject: Re: [PHP-DEV] [RFC][VOTE] Constructor behaviour of internal classes
From: mike@php.net (Michael Wallner)

--Apple-Mail=_F29A594F-C308-4AF5-AC41-4396DA7F3C9C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On 15 03 2015, at 17:09, Dan Ackroyd <danack@basereality.com> wrote:
>=20
> Hi List,
>=20
> The 'Constructor behaviour of internal classes' RFC is now in voting.
> Please note, it's the coding standard that is being voted on. If
> anyone thinks I've implemented the changes in a way that is less
> awesome then there is no reason the changes couldn't be improved.
>=20
> Additionally, while writing the change I noticed some things that were
> already present in the code, that are outside the scope of the RFC but
> ought to be fixed for the release of PHP 7.
>=20
> * Multiple examples of a generic Exception being thrown rather than a
> specific exception being thrown.
>=20
> * Code generating an error notice and throwing an exception. It should
> be one or the other, not both.
>=20
> * The text of exceptions in Intl not always being as informative as
> the error message, which could be improved.
>=20
> But as I said, the vote is on whether the standard behaviour of either
> returning a working instance or throwing an exception, is the standard
> behaviour we want in PHP.
>=20
>=20

For the lazy people, like me:
https://wiki.php.net/rfc/internal_constructor_behaviour#voting =
<https://wiki.php.net/rfc/internal_constructor_behaviour#voting>



--Apple-Mail=_F29A594F-C308-4AF5-AC41-4396DA7F3C9C--