Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91008 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 97781 invoked from network); 29 Jan 2016 08:32:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jan 2016 08:32:54 -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:39919] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DB/C0-24533-3B32BA65 for ; Fri, 29 Jan 2016 03:32:52 -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 337E44B016D; Fri, 29 Jan 2016 09:30:45 +0100 (CET) To: Martin Keckeis References: <56AA7824.1090909@php.net> Cc: Internals Message-ID: <56AB23AA.10806@php.net> Date: Fri, 29 Jan 2016 09:32:42 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: 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: Re: [PHP-DEV] Allow loading extensions by name From: francois@php.net (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=) Hi, Le 29/01/2016 08:09, Martin Keckeis a écrit : > Hello, > > 2016-01-28 21:20 GMT+01:00 François 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 >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > i generally like it. Small improvement and optional. > > In your PR you wrote >> A typical example is the coexistence of a Windows development environment > and a Linux production. In such cases, it is impossible to write a single > configuration file that will work in both environments, forcing developers > to manually maintain two separate versions of the file. > > That will also not work (in some cases) with this change either. > > Some other settings can also be OS dependent > - error_log > - mail.log, SMTP, sendmail_path > - some session settings > - some path settings > -... > > > I think 100% portability will not be achieved very soon You're right, incompatibilities will remain everywhere absolute paths are provided but, in many cases, the only differences are the 'extension=' lines. Anyway, the main objective of this RFC is to hide the platform-specific details of extension file names, making life easier for beginners and documentation/script maintainers. Regards François