Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95235
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.47 as permitted sender)
To: internals@lists.php.net
References: <f790ef52-0a92-a8a3-bb3d-891713b390be@gmail.com>
 <CAF+90c8Qjze6ttRj1F0ZsX=aFfheuHZnLr7t0Y0D-SH79xS6jg@mail.gmail.com>
 <a2ab898f-9463-52c4-bfa1-2e80aa4decdb@lsces.co.uk>
 <CAJW__o1mchg7NymuKrWYxqeu6vVzP6pfyDEpFNNWrhKBJ0N5Bg@mail.gmail.com>
 <e83dfc59-a27b-9a29-3e4f-bbcf9cf0b6c2@lsces.co.uk>
 <CAJW__o3Cxu+xYJiO2ZjbU96HE5ro9GFB0-CHHR+Cf3-beT8WQg@mail.gmail.com>
 <53c8bb5d-3d60-6019-d089-93d0285bb8ff@lsces.co.uk>
 <CAJW__o06BoPfQJaeRSzKtD5oB2hB5b16E4dgCw=aSpHxUoqRuQ@mail.gmail.com>
 <b62916b1-8822-1593-f9d3-47bf98fbfcaf@lsces.co.uk>
 <CAJW__o1Q9ZmLCaBds3HXbeTrbaHLTawsA=pxD0kQ6idNfx9dqw@mail.gmail.com>
 <982dfdae-5c44-5ffc-c3c6-66e361839a67@lsces.co.uk>
 <bc82a2ad-0da9-ce23-5b33-b6d29e6b4385@gmail.com>
 <7ee557d1-1d8e-749f-2310-8a8e946e5270@lsces.co.uk>
Message-ID: <d070b0cb-3a26-c68a-8ea3-8c4bb9efbc2e@gmail.com>
Date: Tue, 16 Aug 2016 16:24:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <7ee557d1-1d8e-749f-2310-8a8e946e5270@lsces.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] orphan extensions cleanup
From: rowan.collins@gmail.com (Rowan Collins)

Hi Lester,

On 16/08/2016 16:16, Lester Caine wrote:
> I have no
> problems with the test side and we have a stable test suite for testing
> against outside of PHP but many of the 'changes' in the code base ARE
> generic changes to some core process and trying to mirror them into an
> unmaintained extension is the problem here. Only people who understand
> WHY they are making a change which affects every extension really know
> how to do that.

That does make sense: a maintainer needs a combination of knowledge of 
the PHP/Zend internals, and the third-party library / API the extension 
is targetting. That's a tough combination to find.