Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86002
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender)
MIME-Version: 1.0
References: <CAMZ7uYexNm6Fy42GYCUW9MPnFWEun=JFOPPSa+-mxOPL7hpaGg@mail.gmail.com>
 <553FB63A.80505@birkholz.biz>
In-Reply-To: <553FB63A.80505@birkholz.biz>
Date: Tue, 28 Apr 2015 21:49:30 +0000
Message-ID: <CACwt+JcnP3sdpYk+=aok-v0XkffKAiCtvZ-iiUtybOC0yfFOig@mail.gmail.com>
To: Dennis Birkholz <dennis@birkholz.biz>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=f46d043c096e6a407a0514cfd671
Subject: Re: [PHP-DEV] [RFC][VOTE] Improved Error Callback Mechanism
From: patrickallaert@php.net (Patrick ALLAERT)

--f46d043c096e6a407a0514cfd671
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Dennis,

Le mar. 28 avr. 2015 =C3=A0 18:33, Dennis Birkholz <dennis@birkholz.biz> a
=C3=A9crit :
>
> just to satisfy my personal curiosity: how can this RFC target 7.0 which
> had the feature freeze over a month ago? Should it not be 7.1 just to
> treat all contributors equal?
>

We are fully aware of the feature freeze and have no intention to bypass
anything.

This is not about a feature "per se": it's just about being able to hook at
some place in the engine with no userland changes, BC breaks or even ABI
changes. In fact, something that doesn't *require* an RFC at all (like the
many commits happening in master, not bound to any specific RFC).

Can we consider that this RFC is for documentation purpose mostly? This is
how we see it and the reason we created it.

Cheers,
Patrick

--f46d043c096e6a407a0514cfd671--