Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69631
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH-PCH6Xm-RJQpf9iPk9HJXM4jjop8J62WE=Uf_MFHQQTDKG2Q@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> <CAH-PCH6Xm-RJQpf9iPk9HJXM4jjop8J62WE=Uf_MFHQQTDKG2Q@mail.gmail.com>
Date: Thu, 17 Oct 2013 11:15:47 -0400
Message-ID: <CAFp73Xu+7q+kM1z8v8E+mh7ZpuNkP4oAKdc6am_hP4voF2HT7A@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@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=001a11c1e98006adac04e8f14c08
Subject: Re: [PHP-DEV] Proposal: Introduction of InvalidStateException
From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com")

--001a11c1e98006adac04e8f14c08
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

@Ferenc: Ok, so let's try to wrap all these suggestion in the SPL RFC you
pointed out and vote.

@Levi: I'd suggest to minimize BC breaks if you're willing to get this
merged.
Dunno how to proceed here, but that should be the focus.


On Thu, Oct 17, 2013 at 10:57 AM, Ferenc Kovacs <tyra3l@gmail.com> wrote:

>
>
>
> 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 ambiguo=
us
>> 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 fo=
r
>> 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.
>
> --
> Ferenc Kov=C3=A1cs
> @Tyr43l - http://tyrael.hu
>



--=20
Guilherme Blanco
MSN: guilhermeblanco@hotmail.com
GTalk: guilhermeblanco
Toronto - ON/Canada

--001a11c1e98006adac04e8f14c08--