So is it fair to say that we (Brian and others who are interested) should persue a robust patch that will allow for an Include directive in PHP's ini file that functions like Apache's Include directive?
dave -----Original Message----- From: Wez Furlong [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 10:34 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; Matthew Walker Subject: Re: [PHP-DEV] Re: [RFC] include_ini and include_ini_dir On 09/12/02, [EMAIL PROTECTED] wrote: > On Thu, 12 Sep 2002, Matthew Walker wrote: > > For what it's worth, here's my +1 on enabling a php-parsed .ini file. > > And to > > maintain backwards compatibility, if the file had no php tags in it, it > > could be parsed as per the old .ini method. > > I'm -1 on this complexity. > > Having an include is OK, but making it a PHP Script will make it very > complex, and it's also very hard to implement. Also, do we really need > that? Likewise, I'm -1 on any kind of scripting in the .ini file. I know it's "nice to have" clever features, but considering that there are only a finite number of options and that in most cases these are set only once for a particular build, I don't think we need it. I can understand Brian's intended use for include (but think that they could be OK without it), but there aren't really that many options or situations where you might need such a degree of flexibility for a couple of options. Most of the options can be set within a PHP script anyway. --Wez. -- 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
