On 09/12/02, "Matthew Walker" <[EMAIL PROTECTED]> wrote: > I see very little point in having include /without/ some kind of parsing. > The idea of include is that it lets you dynamically load different pieces > based on some condition.
Me either, but... > Yes, it can make adding little pieces to the config easier to manage, but in > my opinion, that's not enough to make me want it. So my vote stands at +1 > for include+parsing, and +0 for include alone. But php.ini is a simple config file that prepares a few initial values for the engine before it runs. With the exception of a few options, you can set these values from your php code and use all the wonders of PHP for that. The few options that can't be changed are usually "static" for a site or server configuration, and in a shared server arrangement the sapi provides for setting the options on a per "user" basis. So there is little use for scripting the .ini file when you can just write the code using PHP itself. (to the relative newcomers that are keeping this thread alive: *please* read the archives about the discussions in the past on scripting the ini file). Besides, an .ini file is an .ini file - they are *supposed* to be simple! --Wez. -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
