Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91001 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61448 invoked from network); 28 Jan 2016 20:21:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2016 20:21:03 -0000 Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:63330] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5A/B0-53831-C287AA65 for ; Thu, 28 Jan 2016 15:21:01 -0500 Received: from [127.0.0.1] (unknown [82.240.16.115]) (Authenticated sender: flaupretre@free.fr) by smtp2-g21.free.fr (Postfix) with ESMTPSA id 776044B01B7 for ; Thu, 28 Jan 2016 21:18:57 +0100 (CET) To: Internals Message-ID: <56AA7824.1090909@php.net> Date: Thu, 28 Jan 2016 21:20:52 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 160128-2, 28/01/2016), Outbound message X-Antivirus-Status: Clean Subject: Allow loading extensions by name From: francois@php.net (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=) Hi, Can you please give your thoughts about a PR I just created : https://github.com/php/php-src/pull/1741 Loading extensions by name (instead of file name) provides a portable way of specifying extensions in an INI file. Example : extension=bz2 zend_extension=xdebug This will be converted to the right file name, depending on the platform. Of course, current configurations using filenames remain supported (no BC break), but the recommended way of specifying additional extensions in an INI file becomes 'by name' (See example php.ini files). If I get positive returns, I'll write an RFC targeting 7.1. Regards François