Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38426
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain phparch.com from 64.99.136.139 cause and error)
Message-ID: <05db01c8d23b$7fe3fb50$4401a8c0@foxbox>
Reply-To: "Steph Fox" <steph@phparch.com>
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "internals" <internals@lists.php.net>
References: <04a501c8d181$e67c6ec0$4401a8c0@foxbox> <485A9AC3.3050603@zend.com>
Date: Thu, 19 Jun 2008 19:37:13 +0100
Organization: php|architect
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [PATCH] unix path separators in spl
From: steph@phparch.com ("Steph Fox")


>> The attached patch implements spl_unixify_path_separators(). If it's
>
> I'm afraid that automatically applying slash conversions to all results 
> returned by SPL file functions - if that's what this patch does - may be 
> unwanted. This way SPL functions and regular file functions would return 
> different file names, which can be harmful if these names are used as 
> keys, compared, etc.

Paths. Mm, possibly.

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* 
'\', these days it's capable of recognising either separator. So it really 
would just be down to path comparisons.

I'm actually wondering how much harm it would do to make DEFAULT_SLASH 
generic...

- Steph