Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69630
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFp73XvuVewkNVp-i+t4YgOy5T56bDQNPr0B0v41iHLQ2WFi6A@mail.gmail.com>
References: <CAHZZLotdoP1cy=jMdUjrTjQqfggpVkRTXt5GzgX97k2ES5mQQQ@mail.gmail.com>
	<CAFMT4NoG_hQZMbgacjra5ks5AUfcSgDDWUwSqBQDGmwavZxV1Q@mail.gmail.com>
	<CAH-PCH7ucLpP4WyCtfNMG_OgrcpgjYbVaP8Ox4XA_1Y8M=xxqw@mail.gmail.com>
	<CAFp73XvuVewkNVp-i+t4YgOy5T56bDQNPr0B0v41iHLQ2WFi6A@mail.gmail.com>
Date: Thu, 17 Oct 2013 16:57:37 +0200
Message-ID: <CAH-PCH6Xm-RJQpf9iPk9HJXM4jjop8J62WE=Uf_MFHQQTDKG2Q@mail.gmail.com>
To: "guilhermeblanco@gmail.com" <guilhermeblanco@gmail.com>
Cc: Levi Morrison <morrison.levi@gmail.com>, 
	Benjamin Schneider <benjamin.schneider.de@gmail.com>, internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bdc1870e3226504e8f109c8
Subject: Re: [PHP-DEV] Proposal: Introduction of InvalidStateException
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7bdc1870e3226504e8f109c8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 17, 2013 at 4:43 PM, guilhermeblanco@gmail.com <
guilhermeblanco@gmail.com> wrote:

> Ferenc,
>
> How much of this is PHP willing to take as BC break?
> Like changing from one Exception to another (UnderflowException to
> RuntimeException) and removing OutOfRangeException because it is ambiguou=
s
> seems very hard fro PHP to take in a PHP 5.6 for example.
>
> I may have some time to try something, but I wouldn't spend time just for
> the sake of doing if it's gonna be rejected later.
>
> Cheers,
>
>
The current release process (https://wiki.php.net/rfc/releaseprocess)
wouldn't allow it in 5.6, but one could argue that:
1, the usage of these exceptions not that wide-spread
2, the upgrade path (in your example) is pretty simple, replace every
occurance of UnderflowException to RuntimeException in your codebase, (I
would also argue to not remove OutOfRangeException, but rename it as we
already have that used in spl and php code out there could also use it
already), we could even provide tools to help the migration.

but, this is really a hard topic, because it is more of a semantic issue,
and that is a bit weak argument for breaking BC, so this would require a
really thought-out RFC and the voters could still say no.
I think the actual implementation/patch would be really simple, so the hard
part of the task is to figure out the proper naming and hierarchy.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--047d7bdc1870e3226504e8f109c8--