On Thu, 12 Sep 2002, Yasuo Ohgaki wrote:
Brian France wrote:
I have created a patch for two new .ini directives:
include_ini = filename ; relative or full path
include_ini_dir = full directory path
I prefer to use large single config file if it's not
too large. I didn't like
On Thu, 12 Sep 2002, Devon O'Dell wrote:
Not to be a troll, but weren't srm.conf and access.conf deprecated for a
reason?
I think it was the reason that it made configuration less clear. Three
files for one thing isn't just 'right'.
Derick
.
dave
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 12, 2002 12:26 AM
To: Devon O'Dell
Cc: PHP Developers Mailing List
Subject: Re: [PHP-DEV] Re: [RFC] include_ini and include_ini_dir
On Thu, 12 Sep 2002, Devon O'Dell wrote
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
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
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
PROTECTED]
Subject: Re: [PHP-DEV] Re: [RFC] include_ini and include_ini_dir
The last time we had this discussion a few People didn't
liked that kind of flex^H^H^H^Hcomplexity in the include
file.
Hell, you even could just use an PHP source-file for it ... :)
On Thu, Sep 12
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.
Derick
--
PHP Development Mailing List
Am Donnerstag, 12. September 2002 18:20 schrieb David Viner:
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
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
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.
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, 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
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
: 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
I would have to say that I would be +1 for the include feature in the
php.ini file, but -1 for the PHP parsing of the file... I see no need for
that
The include feature could be very usefull so I don't see anything wrong
with the idea since the newbies could just stay away from it?
I see
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.
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
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
18 matches
Mail list logo
