Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65305
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender)
Date: Mon, 28 Jan 2013 21:54:39 +0000 (GMT)
To: Anthony Ferrara <ircmaxell@gmail.com>
cc: "internals@lists.php.net" <internals@lists.php.net>
In-Reply-To: <CAAyV7nEWFMqBhKE-Q=MquMANmWp+p27Dn-X7nA5ocWRDHshEKA@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1301282153530.6128@whisky.home.derickrethans.nl>
References: <CAAyV7nEWFMqBhKE-Q=MquMANmWp+p27Dn-X7nA5ocWRDHshEKA@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] Purpose of voting
From: derick@php.net (Derick Rethans)

On Mon, 28 Jan 2013, Anthony Ferrara wrote:

> I've always approached it as we're voting for the concept (and details)
> provided in the RFC. But it appears that other people have been voting on
> the specifics of the attached patch (so theoretically an RFC could be
> rejected entirely because some people don't like part of the implementation
> in C, but are fine with the PHP details).
> 
> I'll leave out my opinion (and justification) for now, I'm curious what you
> all think...
> 
> Thoughts?

Both the idea and implementation needs to be sound. If not, I vote "no" 
(and that also means "no" when it makes APC's life harder).

cheers,
Derick