Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28219
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.184.238 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=mnfFajpsDR6tkMZFQDmsb7xCXd/wmrE3SoDtkKVjOVd+HeeDaWo0o/cELVgE6e+XFNRnig2QRa0c85WwfL1jWY00hVMfQ4VucKoUx6Ar0z8iG7/jnQ7hezKV22sf+RvlhqAgyifrJtX3H+uXkn30c4+eVKzIGrqd6v7MMhQhNuA=
Message-ID: <fe05d1540703040629j21dc1442k4b2aee57f35d3ed3@mail.gmail.com>
Date: Sun, 4 Mar 2007 15:29:06 +0100
To: "Marcus Boerger" <helly@php.net>
Cc: kingwez@gmail.com, "Arnold Daniels" <info@adaniels.nl>, 
	internals@lists.php.net
In-Reply-To: <1508893792.20070304144812@marcus-boerger.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <45E33990.8030806@adaniels.nl>
	 <1331353216.20070226232944@marcus-boerger.de>
	 <45E37D05.5040000@adaniels.nl>
	 <408821909.20070303232323@marcus-boerger.de>
	 <fe05d1540703040446u201ce0b7we685bd50808e2c0c@mail.gmail.com>
	 <1508893792.20070304144812@marcus-boerger.de>
Subject: Re: [PHP-DEV] suggestion SplFileInfo
From: pierre.php@gmail.com (Pierre)

On 3/4/07, Marcus Boerger <helly@php.net> wrote:
> Sunday, March 4, 2007, 1:46:40 PM, you wrote:
>
> > On 3/3/07, Marcus Boerger <helly@php.net> wrote:
> >> Hello Arnold,
> >>
> >>   I added glob directory stream support. Now you can do two things:
> >>
> >> $d1 = new DirectoryIterator("glob://mydir/*");
> >> $d2 = new DirectoryIterator("mydir/*", DirectoryIterator::USE_GLOB);
> >>
> >> count() stuff will follow.
>
> > I'm not sure it is a good idea to add glob:// stream support. What
> > does it have to do with custom streams? Will we add pcre:// too?
>
> If someone feels he needs pcre:// and can implement it why not.

Heck no :)

> > DirectoryIteratorPattern/Glob($pattern) make much more sense to me.
>
> Feel free to implement it. Until you do so the problem is that
> DirectoryIterator uses streams directory support and cannot do
> anything else. Thus the onlyway to change the way it works is to
> provide other streams. And that is what I did. I chose to go the
> easy route which even might help other people.

It is maybe easy to add that (or pcre for that matter), does it make
sense? It is not really a resource or custom protocol. Glob or pcre
patterns (or any other patterns) are specific filters for a given
URI/paths, but not resources specific paths like zip: file: or phar:.

> > I did not test it but how does it work when used with other protocols?
> > like: ftp://some/path/?
>
> How is that going to work? Glob does not support that. But anyway, why not
> simply test it before complaining?

Can you please not see any comment on your commits or additions as
complains? It is counter productive, annoying and brings nothing but
anger.

> > It may be more useful to add streams support to our glob functions.
> > But it can bring more troubles than expected.
>
> Actually the glob stream is exactly nothing else than streams layer
> for our glob functions.

Yes I saw that. That does not make a glob:// a good idea. In my humble
opinion, it fits better as filter for a iterator (simple loop or
whatever else like DirectoryIterator). I simply fail to see why the
stream must have this.

--Pierre