Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42306
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: PHP Internals List <internals@lists.php.net>
Message-ID: <29AA2691-6BA7-42E8-86A0-3451F9231375@pooteeweet.org>
To: Daniel Convissor <danielc@analysisandsolutions.com>
In-Reply-To: <20081210183302.GA19304@panix.com>
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 21:02:30 +0100
References: <493ECBFD.6060407@chiaraquartet.net> <20081210183302.GA19304@panix.com>
Subject: Re: [PHP-DEV] problem with include_path and write-based file functions
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 10.12.2008, at 19:33, Daniel Convissor wrote:

> Hi:
>
> On Tue, Dec 09, 2008 at 01:50:21PM -0600, Gregory Beaver wrote:
>> 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.
>
> I agree.
>
> To avoid compatibility issues between 5.2 and 5.3, it seems best  
> that the
> behavior not change in 5.3, though an E_DEPRECATED should be raised.
> Then remove the functionality from 6.0.


which brings us back to the fact that we never added a proper way to  
be able to determine if a file exists in the include path or not. this  
is why a lot of people rely on fopen() for this. if we want to clean  
this up, its high time we offer a proper solution for this. and i am  
getting tired of the excuse, that file_exists() should not mess with  
the include path. so lets add a new function or whatever. but this is  
a common enough use case that we finally need to accept that we need  
to provide a good solution.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org