Re: Re: [RFC] include_ini and include_ini_dir
| From: | Matthew Walker | Date: | Thu, 12 Sep 2002 17:24:12 +0000 |
| Subject: | Re: Re: [RFC] include_ini and include_ini_dir | ||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-88269@lists.php.net to get a copy of this message | ||
> On Thu, 12 Sep 2002, Matthew Walker wrote:
>
>> > On Thu, 12 Sep 2002, devon@sitetronics.com 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. ;)