For what it's worth, my posts were intended to be taken sarcastically :) Devon
Original Message: ----------------- From: Matthew Walker [EMAIL PROTECTED] Date: Thu, 12 Sep 2002 11:24:12 -0600 (MDT) To: [EMAIL PROTECTED] Subject: Re: [PHP-DEV] Re: [RFC] include_ini and include_ini_dir > On Thu, 12 Sep 2002, Matthew Walker wrote: > >> > On Thu, 12 Sep 2002, [EMAIL PROTECTED] wrote: >> > >> >> ok, so we should write a mini-language for the ini? or should we >> just make it php? then we just need to scan/interpret it. >> > >> > Nope, sounds like a bad idea for something simple as a .ini file. >> > >> >> 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? > I fail to see why this would be so complex. PHP already has a PHP parser built in (I /hope/!) so it would merely be a matter of invoking it if the first line of the .ini has a PHP opening tag. But then, IANAPD (I Am Not A PHP Developer) so I could be totally off base here. I'll keep quiet now. ;) -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
