Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35525
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.171 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=eS0puDITki5yf4LgQzaGtlW8duuNTXmqrz47At/FvSs++bfiSAPOLqJtQNPvs0cuOwxsn290wUNGsBv4H/FzYw138w70pF4YHUq0CU0VibySu8EZ/yE0VSCkvky4k82gGfzsUd4ZfkoVUfjja/pjYBiDXRFqsCwhYEPgyxvjSM0=
Message-ID: <e2e02fe0802150648xde1fcb0s6f8caf7aa289a04b@mail.gmail.com>
Date: Fri, 15 Feb 2008 07:48:44 -0700
To: jani.taskinen@iki.fi
Cc: "PHP Internals List" <internals@lists.php.net>
In-Reply-To: <47B5A476.602@sci.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <971575499.20080209153315@marcus-boerger.de>
	 <47B56334.9070007@zend.com>
	 <1203070677.10500.12.camel@localhost.localdomain>
	 <47B568A6.9060704@zend.com>
	 <1158304008.20080215122414@marcus-boerger.de>
	 <47B58B5D.9020301@zend.com> <47B5917C.5050606@sci.fi>
	 <81BAF097-DF7D-4A3D-AED6-A22C912C83DB@daleenterprise.com>
	 <47B5A3E5.4020006@zend.com> <47B5A476.602@sci.fi>
Subject: Re: [PHP-DEV] [RFC] Conditional INI support
From: chrisstocktonaz@gmail.com ("Chris Stockton")

It might be to late to keep it simple, once you add basic language
components like IF-ELSE as you can see people already want basically
another programming language embedded into it. It is my opinion that
the INI files should be simple configuration files. Otherwise they
will become more and more feature rich and people will start shifting
program complexity from the PHP application to the INI file. This
might not be the intention of the people in this list as you are all
pretty sharp, but have you read some of the online tutorials on php? I
just think this kind of feature would be badly abused...

-Chris

On Fri, Feb 15, 2008 at 7:40 AM, Jani Taskinen <jani.taskinen@sci.fi> wrote:
> Dmitry, please don't throw gasoline on the flames.
>  We have to keep the ini files as simple as possible, this isn't the job of
>  the ini file.
>
>  --Jani
>
>
>  Dmitry Stogov kirjoitti:
>
>
> > The idea makes sense too, but mix of C and SH syntax isn't good.
>  >
>  > Dmitry.
>  >
>  > BuildSmart wrote:
>  >> Now that what-if's are occurring in the theoretical world of
>  >> intelligent INI, what about file testing capabilities so that the
>  >> following can be used to preload extensions by existance?
>  >>
>  >> #if -f ${EXTENSIONS_DIR}/gd.so
>  >> extension=gd.so
>  >> #endif
>  >>
>  >> or some other syntax that allows testing to include an extension
>  >> On Feb 15, 2008, at 8:19 AM, Jani Taskinen wrote:
>  >>
>  >>>
>  >>> Currently UNDEFINED would be just string 'UNDEFINED'.
>  >>> Doesn't atoi() for non-numeric string make it 0 ??
>  >>> (or null..:) So that would work without changing anything..
>  >>>
>  >>> --Jani
>  >>>
>  >>> Dmitry Stogov kirjoitti:
>  >>>> I think it will work.
>  >>>> #ifdef UNDEFINED > 5  (false)
>  >>>> #ifdef UNDEFINED <= 5 (true)
>  >>>> (but anyway I think it is possible to find out an unclear condition)
>  >>>> Dmitry.
>  >>>> Marcus Boerger wrote:
>  >>>>> Hello Dmitry,
>  >>>>>
>  >>>>>   shouldn't this be like in C/C++ where a non existing value is
>  >>>>> treated like
>  >>>>> an empty string which behaves like false in boolean evaluations?
>  >>>>>
>  >>>>> marcus
>  >>>>>
>  >>>>> Friday, February 15, 2008, 11:25:42 AM, you wrote:
>  >>>>>
>  >>>>>> #if defined(PHP_MAJOR_VERSION) && PHP_MAJOR_VERSION >= 6
>  >>>>>> extension="unicode.so"
>  >>>>>> #endif
>  >>>>>
>  >>>>>> Here PHP_MAJOR_VERSION is a PHP constant that is not defined in
>  >>>>>> php-5.3 but might be defined in the future version.
>  >>>>>
>  >>>>>> Dmitry.
>  >>>>>
>  >>>>>
>  >>>>>> Jani Taskinen wrote:
>  >>>>>>> On Fri, 2008-02-15 at 13:02 +0300, Dmitry Stogov wrote:
>  >>>>>>>> Jani Taskinen wrote:
>  >>>>>>>>>> c) We can use just "value" insted of ${value} in conditions.
>  >>>>>>>>> Yup. ${foobar} is actually not any "variable" per se, but just a
>  >>>>>>>>> reference to existing ini entry in the file. And I don't think
>  >>>>>>>>> that
>  >>>>>>>>> needs to change.
>  >>>>>>>> Oh, I see. Then we can use just "$string" (or "$str.str") for
>  >>>>>>>> ini entries and "string" for PHP constants. We can also
>  >>>>>>>> implement defined() macro-function, to check if constant defined.
>  >>>>>>> Why? Don't make php.ini parsing any more complex than it already
>  >>>>>>> is(n't).
>  >>>>>>> Any string which can pass as constant will have that constant's (or
>  >>>>>>> environment variable) value. Why do you need any "variable" in there
>  >>>>>>> anyway? And why do you need defined() ??? (examples please? :)
>  >>>>>>>
>  >>>>>>> --Jani
>  >>>>>>>
>  >>>>>
>  >>>>>
>  >>>>>
>  >>>>>
>  >>>>> Best regards,
>  >>>>>  Marcus
>  >>>>>
>  >>>
>  >>> --
>  >>> PHP Internals - PHP Runtime Development Mailing List
>  >>> To unsubscribe, visit: http://www.php.net/unsub.php
>  >>>
>  >>>
>  >>
>  >> -- Dale
>  >>
>  >>
>  >>
>
>  --
>  PHP Internals - PHP Runtime Development Mailing List
>  To unsubscribe, visit: http://www.php.net/unsub.php
>
>