I think php.net/ini going to the right place would be good. So I guess "ini" would be my suggestion.
-Rasmus On Tue, 15 Jan 2002, Gabor Hojtsy wrote: > Hi! > > We just noticed a major problem in the docs, and so we > would like to invent a new name for php.ini settings. > > Now look at > http://www.php.net/manual/en/install.configure.php and > http://www.php.net/manual/en/configuration.php pages > > I am sure that it is confusing for people, to have two > completely different sections, with names consequently > starting with "config" [configuration and configure options]. > > We should invent another name for php.ini directives, > eg. "settings" or some other word, that is easily > distinquisable from "configure". I was also confused for > some days when I first saw these two chapters (years > ago ;). > > Yes, you can say, that we have a note on the configure > options page, that these are compile time options. > > But there are many places, where we refer to "configure > options", and "configuration directives" (yes, we use > these two phrases for the two distinct things). > > Consider the massive base of Windows users, who even > don't know what is configure, and what to do with > configure options, while they are interested in php.ini > settings. > > IMHO it is not corrent to name php.ini settings as > "configuration directives", as we refer to them now... > > Is "setting" / "ini setting" / "ini directive" / "directive" > the right name to use for php.ini directives, and > "configure option" to use for configure options? > > Goba > > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
