Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93178 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34607 invoked from network); 10 May 2016 22:27:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 May 2016 22:27:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=francois@php.net; 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:59938] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 40/EC-63163-E3062375 for ; Tue, 10 May 2016 18:27:11 -0400 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 1E52320037A; Tue, 10 May 2016 22:17:16 +0200 (CEST) To: Lester Caine , 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> <57323F8E.1080800@lsces.co.uk> Message-ID: <1ce20005-706c-52d0-a0f3-67cecdb3e9b8@php.net> Date: Wed, 11 May 2016 00:27:04 +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: <57323F8E.1080800@lsces.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 160510-2, 10/05/2016), Outbound message X-Antivirus-Status: Clean Subject: Re: [PHP-DEV] [RFC] Allow loading extensions by name From: francois@php.net (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=) Hi, Le 10/05/2016 à 22:07, Lester Caine a écrit : > 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çois --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus