Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93197
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.161.173 cause and error)
MIME-Version: 1.0
In-Reply-To: <1ce20005-706c-52d0-a0f3-67cecdb3e9b8@php.net>
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>
Date: Wed, 11 May 2016 05:59:04 +0100
Message-ID: <CAL=_i_kMYnpVCeqrQmNhdpWYRb4K0WJTMxWYUy2R8sRHvUSMDg@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@php.net>
Cc: Lester Caine <lester@lsces.co.uk>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c0775bca229eb053289e673
Subject: Re: [PHP-DEV] [RFC] Allow loading extensions by name
From: pthreads@pthreads.org (Joe Watkins)

--94eb2c0775bca229eb053289e673
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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.

Cheers
Joe

On Tue, May 10, 2016 at 11:27 PM, Fran=C3=A7ois Laupretre <francois@php.net=
>
wrote:

> Hi,
>
>
> Le 10/05/2016 =C3=A0 22:07, Lester Caine a =C3=A9crit :
>
>> Windows did not worry about which extension was used
>> in the past, but nowadays the problem is ensuring the correct build of
>> extension is accessed and while 32bit is still the safer base, it's all
>> too easy to get them mixed up with 64bit builds. All of MY recent
>> windows installs have had to be 32bit so this creates a conflict with
>> PHP7's assumption that modern target will be 64bit ;) TODAY the windows
>> php.ini needs to be managed to ensure that the correct paths are used to
>> the correct build, and personally I'd rather not 'simplify' something
>> which has a much bigger impact - and adding a build identifier to the
>> file name may be a better fix than trying to rely on the path to ensure
>> the correct build is accessed.
>>
>
> Right. We could include a build ID in file names. And adapt the way we
> compute file names from extension names. But I don't see how this concern
> conflicts with the RFC.
>
> Regards
>
> Fran=C3=A7ois
>
> ---
> L'absence de virus dans ce courrier =C3=A9lectronique a =C3=A9t=C3=A9 v=
=C3=A9rifi=C3=A9e par le
> logiciel antivirus Avast.
> https://www.avast.com/antivirus
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--94eb2c0775bca229eb053289e673--