Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38424
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <485AA7CB.5040503@zend.com>
Date: Thu, 19 Jun 2008 11:39:07 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Steph Fox <steph@phparch.com>
CC: internals <internals@lists.php.net>
References: <04a501c8d181$e67c6ec0$4401a8c0@foxbox> <485A9AC3.3050603@zend.com> <05db01c8d23b$7fe3fb50$4401a8c0@foxbox>
In-Reply-To: <05db01c8d23b$7fe3fb50$4401a8c0@foxbox>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [PATCH] unix path separators in spl
From: stas@zend.com (Stanislav Malyshev)

Hi!

> On the other hand, the only code likely to be broken would be 
> platform-specific code written for Windows boxes - how much of that is 
> likely to be out there? Another point is that, although Windows *writes* 

Any amount, but I don't see why it would break only windows-specific 
code. If I use any other function to get filenames, and/or use 
PATH_SEPARATOR to compose names, and then use these names in the same 
context as those converting SPL function, I'd get different names on 
Windows even if my application was written in most generic way. Do I 
miss something?

> '\', these days it's capable of recognising either separator. So it 
> really would just be down to path comparisons.

Path comparison is important.
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com