Hi Lester,
Le 10/05/2016 à 21:01, Lester Caine a écrit :
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!
As Fleshgrinder suggested, we can easily search for 'php_<name>.dll' and, if not found, then '<name>.dll'. This would occur on Windows only.
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.
Using extension names instead of file names will also be supported in individual .ini files, just as in the main php.ini.
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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
