Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42311
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: internals Mailing List <internals@lists.php.net>
Message-ID: <025EE4A9-DCB9-4B66-9D87-27174E0AF81A@pooteeweet.org>
To: Gregory Beaver <greg@chiaraquartet.net>
In-Reply-To: <493ECBFD.6060407@chiaraquartet.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 17 Dec 2008 22:44:11 +0100
References: <493ECBFD.6060407@chiaraquartet.net>
Subject: Re: [PHP-DEV] problem with include_path and write-based file functions
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 09.12.2008, at 20:50, Gregory Beaver wrote:

> file, it should only be used to find existing files.  In any case, I
> think allowing include_path to be used at all for file modification is
> horrendous, and think it should be deprecated and removed from PHP 6.
> We should simply add file_resolve_path() function which can be used to
> locate a file.


Since we have stream_resolve_include_path(), I guess we can make this  
suggestion a reality.
Deprecate the ability to mess with the include path in fopen()/ 
file_get_contents() or any other method/function that can do write  
operations. this btw imho also includes the cases when these functions  
(for example fopen()) are using in read mode.

Speak now or forever hold your peace ..

regards,
Lukas Kahwe Smith
mls@pooteeweet.org