Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93167
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
To: internals@lists.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>
Message-ID: <57323F8E.1080800@lsces.co.uk>
Date: Tue, 10 May 2016 21:07:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <8d5a0962-021b-cd38-1946-47d1bad24af0@fleshgrinder.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Allow loading extensions by name
From: lester@lsces.co.uk (Lester Caine)

On 10/05/16 20:18, Fleshgrinder wrote:
> WIN: `php -d extension=php_foo.dll -d zend_extension=php_bar.dll`

I would be most surprised to find windows users running php command
line, but I suppose I am somewhat out of the loop on that side. All my
windows users run PHP on a web server and have trouble even accessing
the command line.

I don't think .so extension is still being used on windows installs.
THAT was another 'fix' used to make installation of third party
extensions easier. 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.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk