Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85389
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAPg3XxKG3g=Oh79+_woyBedyP2CFkWPFLKnNuCuX6nTn0f6GKA@mail.gmail.com>
References: <CAPg3XxKG3g=Oh79+_woyBedyP2CFkWPFLKnNuCuX6nTn0f6GKA@mail.gmail.com>
Date: Sun, 22 Mar 2015 01:30:35 +0000
Message-ID: <CAPwsocGiGMS0GT9jERMNRboe_nC=sGZjYWFr=AhmOGP0WncJrQ@mail.gmail.com>
To: Peter Cowburn <petercowburn@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1134038204c5c50511d67f72
Subject: =?UTF-8?B?UmU6IFtQSFAtREVWXSBUbyBSRkMgb3IgTm90IFRvIFJGQyBbd2FzIFJlOiBbUEhQLURFVg==?=
	=?UTF-8?B?XSDlm57lpI3vvJogW1JGQ11bRElTQ1VTU0lPTl0gQWRkIHByZWdfcmVwbGFjZV9jYWxsYmFja19hcnJh?=
	=?UTF-8?B?eSBmdW5jdGlvbl0=?=
From: leight@gmail.com (Leigh)

--001a1134038204c5c50511d67f72
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 21 March 2015 at 12:30, Peter Cowburn <petercowburn@gmail.com> wrote:

> On 21 March 2015 at 08:14, Xinchen Hui <laruence@php.net> wrote:
>
> > Hey:
> >
> > On Fri, Mar 20, 2015 at 9:14 PM, Xinchen Hui <laruence@php.net> wrote:
> > > Hey:
> > >
> > > On Fri, Mar 20, 2015 at 7:53 PM, Alain Williams <addw@phcomp.co.uk>
> > wrote:
> > >> On Fri, Mar 20, 2015 at 10:46:58PM +1100, Pierre Joye wrote:
> > >>> On Fri, Mar 20, 2015 at 7:03 PM, Wei Dai <zxcvdavid@gmail.com>
> wrote:
> > >>> > Hi internals,
> > >>> >> Hi internals,
> > >>> >>
> > >>> >> The RFC to add a user-land function for an easy-to-use and
> reliable
> > >>> >> preg_replace_callback_array() in PHP is up for discussion:
> > >>> >> https://wiki.php.net/rfc/preg_replace_callback_array
> > >>> >>
> > >>> >> This proposes adding one function: `preg_replace_callback_array(=
)`
> > that
> > >>> >> is the better way to Implement when there are multiple patterns
> > need to
> > >>> >> replace.
> > >>> >>
> > >>> >> I would love to hear your feedback! :)
> > >>> >> Any objections?
> > >>> >
> > >>> > I=E2=80=99ve sent this mail for four days, I don=E2=80=99t know i=
f this RFC needs a
> > vote.
> > >>> > If you guys have no objections on this, please review the code an=
d
> > merge it,
> > >>> > thanks.
> > >>>
> > >>> Nice job, i like the idea.
> > >>>
> > >>> I am not sure about a RFC or not. It somehow looks like a sane
> > >>> replacement for something we killed (with good reasons).
> > >>>
> > >>> Let see what the other think :)
> > >>
> > >> I used s/something/code/ge in a perl script that I wrote a few days
> > ago. Very
> > >> useful. It would have been a lot more work to do it another way.
> > >>
> > >> So: +1 to the ability to do this, regardless of what mechanism is
> > eventually chosen.
> > >
> > > I also +1 for this.
> > >
> > > if there is no objections raises, I am going to merge it tomorrow..
> > merged
> >
> > thanks
> >
>
>
>
> Whoa, hold on there a second.
>
> An RFC was created, presumably intending to follow that line of procedure=
.
> Then Xinchen comes along and puts a middle finger up to the whole process=
,
> reverts back to the old "if no-one complains by tomorrow, merge it"
> approach, then does the merge.
>
> I'm all for avoiding the potentially unnecessary red tape of the RFC
> process. Particularly for small, standalone changes like this. I fear the=
re
> are other who aren't so lenient.
>
> Thoughts?..
>

Yep, this does look like another case of simply ignoring rules. The fact
that what does and does not require an RFC does not help, this probably
didn't need one, however one was created and the rules need to be stuck to.

Instead of forcing this change to be reverted, because it really is
self-contained, we need a succinct wiki document on what does and doesn't
require an RFC.

--001a1134038204c5c50511d67f72--