Le 11/05/2016 à 06:59, Joe Watkins a écrit :
Morning,
In this case, it is currently impossible to write a single
configuration file that will work in both environments, forcing
developers to manually maintain two separate versions of the file.
I'm aware this has been mentioned in this thread, and I've read the open
issue disclaimer.
The RFC does not solve the problem it is trying to solve.
It's still going to be impossible to have a single configuration file.
The only win seems to be when using php from the command line, or in
documentation.
Since the mechanism for loading extensions has been the same for so
long, and since that knowledge is well dispersed among those who require
it, I'm not really seeing the point in changing anything.
The idea that we could one day have a configuration file for both
platforms seems like a pipe dream, so this can't really be considered a
"step closer" to that; It's never going to happen.
I realize that I shouldn't have mentioned the possibility to unify
Windows/Unix configurations, even if I personally have cases where
WIndows & Unix INI files need to be duplicated just because of
'extension=' lines. Once again, we are stuck in 'if it doesn't solve
everything, it's useless'.
So, please consider it just make things easier for documentation writers
and end-users. You may think that 'the knowledge is well dispersed' but,
about every months, I see people from project teams coming at me and
asking why the 'extension=php_xxx.dll' line they found on Internet
doesn't work on their Linux installation. After years of similar
requests, I'm proposing this change. But I'm probably wrong and it is
clear that everyone in the world has the same knowledge about PHP as
yours or mine!
Regards
François
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
