Re: config.w32.h...registry configuration

I'm in favour of looking for php.ini in the same dir as the executeable module - as in the path part of GetModuleFileName(), so it will work for DLL as well as EXE versions. I'm a bit dubious of using the registry for configuring PHP, particularly when multiple installations/versions are present; I'm not actively against it, as it will no doubt prove useful to quite a few people, but personally, I would not use it. --Wez. On 02/05/02, "Zeev Suraski" <zeev@zend.com> wrote: > Does anybody have an opinion about this? > If we go for that solution, should we remove the CWD lookup? My personal > belief is that we should, but it may have to do with my perception of what > this feature is useful for. Other people may be using the CWD lookup for > different things. > (Note: it's been pointed out that the CWD lookup can be a potential > security risk, because it allows people to override php.ini in some shared > hosting environment setups, so it's another reason to replace it with the > path lookup) > > Zeev > > At 23:17 01/05/2002, Zeev Suraski wrote: > >At 23:11 01/05/2002, Shane Caraveo wrote: > >>That would only solve that particular situation, what about multiple > >>installations of the same version, or seperate configurations for the > >>same installation? > > > >We can have PHP look for php.ini in the directory where php.exe is > >located. This would allow you to easily configure different INI settings > >for different versions. > >That's kind of what I wanted to do years ago, but ended up making it look > >for php.ini in the CWD, which is not all that helpful. > > > >Zeev > > > > > >-- > >PHP Development Mailing List <http://www.php.net/> > >To unsubscribe, visit: http://www.php.net/unsub.php > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php