Re: problem with include_path and write-based file functions
| From: | Lukas Kahwe Smith | Date: | Wed, 17 Dec 2008 21:30:14 +0000 |
| Subject: | Re: problem with include_path and write-based file functions | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-42309@lists.php.net to get a copy of this message | ||
On 17.12.2008, at 22:24, Hannes Magnusson wrote:
On Wed, Dec 17, 2008 at 21:02, Lukas Kahwe Smith <mls@pooteeweet.org> wrote:cool. talk about a convoluted function name. the documentation is probably not what we want though: "stream_resolve_include_path — Determine what file will be opened by calls to fopen() with a relative path" it should rather talk about being able to determine what (if anything) would be loaded on an include call. regards, Lukas Kahwe Smith mls@pooteeweet.orgwhich 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 lotThat is simply not true. stream_resolve_include_path() is available in HEAD.