Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40278
Return-Path: <tony@daylessday.org>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 86391 invoked from network); 5 Sep 2008 07:01:12 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 5 Sep 2008 07:01:12 -0000
Authentication-Results: pb1.pair.com smtp.mail=tony@daylessday.org; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=tony@daylessday.org; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender)
X-PHP-List-Original-Sender: tony@daylessday.org
X-Host-Fingerprint: 89.208.40.236 mail.daylessday.org Linux 2.6
Received: from [89.208.40.236] ([89.208.40.236:46053] helo=daylessday.org)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 26/30-19226-639D0C84 for <internals@lists.php.net>; Fri, 05 Sep 2008 03:01:11 -0400
Received: from [192.168.3.254] (unknown [212.42.62.198])
	by daylessday.org (Postfix) with ESMTP id 57B7A6401F6;
	Fri,  5 Sep 2008 11:01:07 +0400 (MSD)
Message-ID: <48C0D927.7050600@daylessday.org>
Date: Fri, 05 Sep 2008 11:00:55 +0400
User-Agent: Thunderbird 2.0.0.12 (X11/20071114)
MIME-Version: 1.0
To: Stan Vassilev | FM <sv_forums@fmethod.com>
CC: PHP Internals List <internals@lists.php.net>
References: <20080904190717.aaz97tz688oogc4c@horde.chinstrap.eu> <48C01A91.6010501@daylessday.org> <1F1F55D1526B4BA1999B314C72CF56A6@pc>
In-Reply-To: <1F1F55D1526B4BA1999B314C72CF56A6@pc>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] ini-parsing, double quotes, windows in 5.3
From: tony@daylessday.org (Antony Dovgal)

On 04.09.2008 23:08, Stan Vassilev | FM wrote:
> There won't be any bug reports, if the ini parser detects improper backslash 
> usage (i.e., using a backslash with a following character which doesn't form 
> correct escape combination) and stops with informative and descriptive 
> message explaining the parser changes.  Then anyone who can read, will 
> figure it out, and fix it. 

Did you actually read what Johannes said?
"c:\Documents\tony" is perfectly legal string in both cases.
But in 5.3 it means "c:\Documents<tab>ony" and this is THE problem.
No error messages, no explanation whatsoever.

-- 
Wbr, 
Antony Dovgal