Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93230
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>
 <124101109CE9C1419F74344AA1F1CCB82810150353@Ikarus.ameusgmbh.intern>
 <b3bd9416-9b85-243d-11b7-71a0011be18a@php.net>
Message-ID: <57332104.6050209@lsces.co.uk>
Date: Wed, 11 May 2016 13:09:40 +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: <b3bd9416-9b85-243d-11b7-71a0011be18a@php.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: AW: [PHP-DEV] [RFC] Allow loading extensions by name
From: lester@lsces.co.uk (Lester Caine)

On 11/05/16 12:53, François Laupretre wrote:
> Le 11/05/2016 à 08:20, Christian Stoller a écrit :
>>> -----Ursprüngliche Nachricht-----
>>> Von: François Laupretre [mailto:francois@php.net], Gesendet:
>>> Dienstag, 10. Mai 2016 15:23
>>>
>>> Please read and comment :
>>>
>>> https://wiki.php.net/rfc/load-ext-by-name
>> Why not just naming them *.so on all platforms and removing the "php_"
>> prefix on Windows?
>>
>> Apache modules on Windows also have the .so suffix.
> 
> AFAIK, the 'php_' prefix is required on WIndows because, without it,
> some extension file names would conflict with system DLLs. The only way
> to unify names would be to add the php_ prefix everywhere. This is the
> mechanism used by Apache, with the 'mod_' prefix. Unfortunately, PHP
> started on Unix, where the prefix was not needed, and didn't want to
> change the Unix behavior when Windows support was added.
> 
> About the '.so' suffix, some systems don't use this as shared lib
> suffix. HP-UX, for instance, uses '.sl', and others exist, like
> '.dynlib'. On some systems, you cannot load a dynamic library if its
> suffix is not the right one. So , '.so' is not usable everywhere.

One tends to forget the reason some decisions were made, and when
prompted the reasons come back. It's the simple fact that windows will
look in the path to see if it finds a copy of a 'library' which is the
main problem here, and in my case it's finding copies of the gds32.dll
which are the wrong format for the php_interbase.dll extension. I'm
seeing the same problem with other third party clients, so in my book it
is important to keep using the extension so one knows exactly which
files are involved.

But as I said I properly planned revamp of handling extensions does make
sense?

-- 
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