Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117294 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 11629 invoked from network); 7 Mar 2022 12:10:44 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 7 Mar 2022 12:10:44 -0000 To: internals@lists.php.net Date: Mon, 7 Mar 2022 13:33:27 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Content-Language: en-GB References: <392d73ddcf41f4573855ece4b269d872@posteo.de> In-Reply-To: <392d73ddcf41f4573855ece4b269d872@posteo.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Posted-By: 149.241.136.89 Subject: Re: Question: What are requirements for having (new/old) functionswithin PHP core? :) From: marandall@php.net (Mark Randall) Message-ID: On 07/03/2022 12:56, Thomas Krüger wrote: > Or if it has nothing to do with performance, why not including > everything from PECL into PHP core, so PHP could offer out-of-the-box > more and more features for developers? PECL packages get to maintain their own release schedule, unlike PHP which follows a fixed cycle. PECL packages have their own permissions, unlike PHP which only allows a narrow group to merge code into it. The PHP core team does not have the knowledge or time to maintain every PECL package, or even a large number of them. Things distributed in Core should be produced and tested to the same standard as the engine itself. Certain PECL packages conflict such as if they were forked.