Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:4621 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30809 invoked by uid 1010); 30 Sep 2003 18:14:33 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 30750 invoked by uid 1007); 30 Sep 2003 18:14:33 -0000 Message-ID: <20030930181433.30748.qmail@pb1.pair.com> To: internals@lists.php.net Reply-To: "Justin Hannus" References: <005801c3873e$38c71880$4d00a8c0@vandal> <021801c38741$b34407f0$0702a8c0@titan> Date: Tue, 30 Sep 2003 14:11:50 -0400 Lines: 42 Organization: vci X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Posted-By: 63.76.208.30 Subject: Re: [PHP-DEV] file_exists and array_merge_clobber From: jhannus@visualconceptsinc.com ("Justin Hannus") I agree with Wez, what if you are searching for a file with a relative file path, e.g: wrote in message news:021801c38741$b34407f0$0702a8c0@titan... > Using the include path for file_exists doesn't sound useful to me, for > similar reasons as those for not allowing to write a file in the include > path - which file are you actually writing to? What if someone puts a file > with the same name earlier in the include path and so on. > > What is probably better is some kind of generic path-searching function that > returns the full path to the first file in the include_path (or some other > path). > > --Wez. > > ----- Original Message ----- > From: "Lukas Smith" > To: > Sent: Tuesday, September 30, 2003 11:32 AM > Subject: [PHP-DEV] file_exists and array_merge_clobber > > > > Hi, > > > > We have a new intern who got right to work to improve file_exists() to > > also be able to check the include_path similar to how fopen() can.