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.
if we want to make the ini file more powerful, there are *many* things that
can be done... it just really depends how powerful it needs to be
(especially since php works fine without an ini file at all)
devon
Original Message:
-----------------
From: Markus Fischer [EMAIL PROTECTED]
Date: Thu, 12 Sep 2002 18:29:00 +0200
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Re: [RFC] include_ini and include_ini_dir
On Thu, Sep 12, 2002 at 09:20:03AM -0700, David Viner wrote :
> Hmm... in the apache world, the srm.conf and access.conf were deprecated,
> but the Include directive in the configuration file is still maintained.
> That is, by default, people use a single apache configuration file.
> However, for specialized cases, like Brian's, people have the ability to
use
> multiple files if they want the extra work of multiple configuration
files.
Apache also has the <if> tags which makes things even more
useful when it comes to including of optional features.
--
GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc
- It's not a fug, it's a beature. -
--------------------------------------------------------------------
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
