On Sun, May 18, 2014 at 9:01 PM, Zeev Suraski <zeev@zend.com> wrote:
> Well put. In the strangeness of voting on an implementation RFC, I
> don't see how it makes sense to talk about "side effects". They're
> the very essence of the patch and the reason it's being opposed.
>
> If there's a better way to so it, let's see it. The sensible thing to
> do would be implementing it for phpng, seeing a *final* version of the
> patch and it's consequences, and then making an informed decision.
If I get your point correctly, you are asking to provide the final
version of a patch against phpng, which is not even in alpha stage,
mvoing target and APIs, etc. That's not possible.
> Even without it, Nikita's proposal seems as a much better baseline
> everyone can agree on.
It would help if you actually read replies instead of systematically
negate this proposal and how things are supposed to work here. Let
alone the calls for -1 based on wrong numbers and facts. This is wrong
in so many ways.
Now, what would have happened if we did what you are saying for
opcache? It would most likely not be in the voting phase if we
consider all supported platforms or changes happening since the votes
began. It would be time to be a little bit serious and consistent if
you really want to agree on something.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org