Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35542
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 64.97.136.146 cause and error)
Message-ID: <00b001c870bf$22ec6000$c6fc1f3e@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Marcus Boerger" <helly@php.net>,
	"Lukas Smith" <smith@backendmedia.com>
Cc: "Dmitry Stogov" <dmitry@zend.com>,
	"PHP Internals List" <internals@lists.php.net>,
	<jani.taskinen@iki.fi>,
	"Andi Gutmans" <andi@zend.com>,
	"Jani Taskinen" <jani.taskinen@sci.fi>
References: <971575499.20080209153315@marcus-boerger.de>  <47B54F0C.2090700@zend.com>  <1203067815.10500.5.camel@localhost.localdomain>  <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> <006001c87037$f9633600$c6fc1f3e@foxbox> <898481503.20080216110509@marcus-boerger.de>
Date: Sat, 16 Feb 2008 17:12:36 -0000
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Conditional INI support
From: steph@zend.com ("Steph Fox")

Hi Marcus,

>  so here's my take on the matters. For 5.4 we collect ideas and implement
> them. So that 5.4 comes out with mostly PECL. I guess we can collect 
> action
> items on Lukas' wiki.

Greg tells me he's been working so hard on ext/phar lately that Pyrus is 
still pre-alpha - it's not going to be ready in time for 5.3. So your 
approach sounds good to me...

Lukas?

- Steph

>
> marcus
>
> Saturday, February 16, 2008, 2:05:06 AM, you wrote:
>
>> I'm with Dmitry - but syntax aside, the only way this becomes even 
>> halfway
>> important is if the whole PECL scenario is sorted out in a way that makes
>> good sense to the end users.
>
>> Back to square one. Sorry guys but sooner or later this has to be dealt
>> with. We need to be sure of what a PHP installation is likely to mean... 
>> to
>> everybody.
>
>> - Steph
>
>> ----- Original Message ----- 
>> From: "Dmitry Stogov" <dmitry@zend.com>
>> To: "PHP Internals List" <internals@lists.php.net>
>> Cc: <jani.taskinen@iki.fi>; "Marcus Boerger" <helly@php.net>; "Andi 
>> Gutmans"
>> <andi@zend.com>; "Jani Taskinen" <jani.taskinen@sci.fi>
>> Sent: Friday, February 15, 2008 2:38 PM
>> Subject: Re: [PHP-DEV] [RFC] Conditional INI support
>
>
>>> 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
>>>
>
>
>
>
> Best regards,
> Marcus
>