On 10/05/16 17:27, Fleshgrinder wrote: >> Please read and comment : >> > >> > https://wiki.php.net/rfc/load-ext-by-name >> > > +1 and I am wondering why nobody else ever came to this idea.
The idea has been proposed before, but the addition of php_ for windows installs has not been universally applied. Extensions like eAccelerator, adodb and other third party extensions that did not form part of the windows 'installation' files. Most of these have been killed off by the restructuring of the core so it's probably less of a problem now than 5 years ago! Another negative is the fact that most Linux installations do not use entries in the php.ini file to enable extensions, preferring to manage them via the package manager. THAT particular practice is something I already copy back to the windows installs, using individual .ini files for each extension, and stripping those extensions and settings from the main php.ini. This is not simply a matter of adding another load mechanism to the mix, so any rfc should perhaps bear in mind all the aspects of 'package management' process? Certainly it's not quite as simple as assuming windows extensions start php_ and end .dll ... -- 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
