Re: CLI SAPI (was Re: [PHP-DEV] 4.3 release call to arms)

> > > I think the only remaining issue here is to be able to have a > > separate > > > config/ini file for cli. While we're at it we might as well > > support > > > SAPI-specific config files, so PHP first looks for php-$SAPI.ini, > > then > > > php.ini. > > > > I think this is a good idea. So cli, for instance, would first look > > for php-cli.ini, and if it fails it would fall back on php.ini. I'll > > have a go at implemeting it. > > > > With this, and Jan's plaintext php -i, i thing cli's feature set is > > complete for now. > > Complete ? :) > > How about system wide ini files and user-specific ones > /etc/php/php(-cli).ini and ~/.php(-cli).ini . > > While we are at it, how about a feature which first also > tries to access the php.ini with for a specific version > number: php-4.3.0-cli.ini > > But this would ultimately also need something like a Include > statement for php.ini so a php-4.3.0-cli.ini could still load > a php-command.ini or so (which is not likely to happen > soon/ever afiak). > > my 2e ;) I did say "for now" :) And why am I not suprised that you would come out from hiding on this one :) Anyway, I say we keep it simple for now (unless someone wants to jump in and implement all of you nice suggestions). Edin