Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91007
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <56AA7824.1090909@php.net>
References: <56AA7824.1090909@php.net>
Date: Fri, 29 Jan 2016 08:09:17 +0100
Message-ID: <CAEp07h99Otco7SVH9dNK8hFgXoW5aOf1rYSdk=xmReij+QKdFw@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@php.net>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c36b66a80437052a73b649
Subject: Re: [PHP-DEV] Allow loading extensions by name
From: martin.keckeis1@gmail.com (Martin Keckeis)

--001a11c36b66a80437052a73b649
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello,

2016-01-28 21:20 GMT+01:00 Fran=C3=A7ois Laupretre <francois@php.net>:

> 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=3Dbz2
> zend_extension=3Dxdebug
>
> 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=C3=A7ois
>
> --
> 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

But regardless of that +1 from a PHP user


Best regards
Martin

--001a11c36b66a80437052a73b649--