Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35519
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain sci.fi from 63.208.196.178 cause and error)
Message-ID: <47B59237.50403@sci.fi>
Date: Fri, 15 Feb 2008 15:23:03 +0200
Reply-To: jani.taskinen@iki.fi
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Marcus Boerger <helly@php.net>
CC: Dmitry Stogov <dmitry@zend.com>, 
 PHP Internals List <internals@lists.php.net>,
 Andi Gutmans <andi@zend.com>
References: <971575499.20080209153315@marcus-boerger.de> <47B54F0C.2090700@zend.com> <1203067815.10500.5.camel@localhost.localdomain> <872209860.20080215122650@marcus-boerger.de>
In-Reply-To: <872209860.20080215122650@marcus-boerger.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Conditional INI support
From: jani.taskinen@sci.fi (Jani Taskinen)

Marcus Boerger kirjoitti:
> Hello Jani,
> 
> Friday, February 15, 2008, 10:30:15 AM, you wrote:
> 
>>> b) I think usage of square brackets is not a good idea, because they are
>>> commonly used to divide ini files into sections. Why not to use C 
>>> syntax? (#if...)
> 
>> I'd prefer that syntax too, it would be much clearer than mixing the
>> sections with this. It's also backwards compatible, lines prefixed with
>> # are simply ignored.
> 
> I am fine with that if someone finds a good way to parse this.

What do you mean with 'good way' ? :) Just parse it strict like CPP does,
so that any of these #if..#else..#elseif..#endif have to start from the first 
column in line, otherwise they're ignored.. (okay, CPP in SOME systems expects 
that.. :)

My version of conditionals does just that. There's nothing special about it..:)
Or I misunderstood what you meant with this.

--Jani