Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93231
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender)
To: Joe Watkins <pthreads@pthreads.org>
References: <59e5902d-004f-33b5-5d6f-991d89371e05@php.net>
 <2461b452-f595-6fa9-4e33-9e163f79d162@fleshgrinder.com>
 <57322FFC.1040109@lsces.co.uk>
 <8d5a0962-021b-cd38-1946-47d1bad24af0@fleshgrinder.com>
 <57323F8E.1080800@lsces.co.uk> <1ce20005-706c-52d0-a0f3-67cecdb3e9b8@php.net>
 <CAL=_i_kMYnpVCeqrQmNhdpWYRb4K0WJTMxWYUy2R8sRHvUSMDg@mail.gmail.com>
Cc: Lester Caine <lester@lsces.co.uk>, PHP internals <internals@lists.php.net>
Message-ID: <5373ed40-b891-a4b9-6b45-7afa4061e160@php.net>
Date: Wed, 11 May 2016 14:10:41 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAL=_i_kMYnpVCeqrQmNhdpWYRb4K0WJTMxWYUy2R8sRHvUSMDg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Allow loading extensions by name
From: francois@php.net (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=)

Le 11/05/2016 à 06:59, Joe Watkins a écrit :
> Morning,
>
>> In this case, it is currently impossible to write a single
> configuration file that will work in both environments, forcing
> developers to manually maintain two separate versions of the file.
>
> I'm aware this has been mentioned in this thread, and I've read the open
> issue disclaimer.
>
> The RFC does not solve the problem it is trying to solve.
>
> It's still going to be impossible to have a single configuration file.
> The only win seems to be when using php from the command line, or in
> documentation.
>
> Since the mechanism for loading extensions has been the same for so
> long, and since that knowledge is well dispersed among those who require
> it, I'm not really seeing the point in changing anything.
>
> The idea that we could one day have a configuration file for both
> platforms seems like a pipe dream, so this can't really be considered a
> "step closer" to that; It's never going to happen.

I realize that I shouldn't have mentioned the possibility to unify 
Windows/Unix configurations, even if I personally have cases where 
WIndows & Unix INI files need to be duplicated just because of 
'extension=' lines. Once again, we are stuck in 'if it doesn't solve 
everything, it's useless'.

So, please consider it just make things easier for documentation writers 
and end-users. You may think that 'the knowledge is well dispersed' but, 
about every months, I see people from project teams coming at me and 
asking why the 'extension=php_xxx.dll' line they found on Internet 
doesn't work on their Linux installation. After years of similar 
requests, I'm proposing this change. But I'm probably wrong and it is 
clear that everyone in the world has the same knowledge about PHP as 
yours or mine!

Regards

François