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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
