Re: problem with include_path and write-based file functions

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