Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99417 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81652 invoked from network); 7 Jun 2017 10:21:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jun 2017 10:21:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@tekwire.net; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=francois@tekwire.net; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain tekwire.net does not designate 212.27.42.4 as permitted sender) X-PHP-List-Original-Sender: francois@tekwire.net X-Host-Fingerprint: 212.27.42.4 smtp4-g21.free.fr Received: from [212.27.42.4] ([212.27.42.4:61501] helo=smtp4-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/47-27119-B93D7395 for ; Wed, 07 Jun 2017 06:21:16 -0400 Received: from [172.16.0.22] (unknown [158.255.108.131]) (Authenticated sender: flaupretre@free.fr) by smtp4-g21.free.fr (Postfix) with ESMTPSA id BEA2819F5D7 for ; Wed, 7 Jun 2017 12:21:11 +0200 (CEST) To: internals@lists.php.net References: <5313411f-40b4-58c6-83a8-7e813526f2a7@tekwire.net> Message-ID: <523cbe62-d237-955a-e11f-87abaacbb816@tekwire.net> Date: Wed, 7 Jun 2017 12:21:11 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <5313411f-40b4-58c6-83a8-7e813526f2a7@tekwire.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: fr Subject: About PCS (was : Proposing inclusion of PCS in the 7.2 core distribution) From: francois@tekwire.net (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=) Hi, thanks to all for taking the time to think about it and give your opinion. It seems that we may gather a consensus on the concept, as most of us seem to agree about the benefits a mechanism like PCS can bring to the core development process in general. It also appears that PCS is not ready for an official release yet. Among others, we need to refine the way PHP code is loaded and registered. So, here is what I'm proposing : - Keep enriching the discussion during about 2 weeks. Please give examples of core extensions that, in your opinion, are susceptible to be partially or fully converted to PHP. Suggestions to complement existing core extensions (like an additional curl OO layer) are welcome too. Please tell us if a PHP implementation of these features already exists somewhere. I would be especially interested by a PHP implementation of the PDO generic layer... - Then, I'll write an RFC summarizing the discussion. The RFC will list blocking and non-blocking issues, as well as an indicative timeline. Target for an initial release will be 7.3. It should leave enough time to solve blocking issues and start converting some existing code to PHP. - This RFC will then be voted upon. The vote will just ensure we agree on the concept and the objectives. It won't authorize the final merge in advance. This will be validated by another vote when the implementation to release is ready. The objective is to avoid restarting the whole discussion when we're ready for a release. Regards François