Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:28220 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8410 invoked by uid 1010); 4 Mar 2007 15:38:30 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 8395 invoked from network); 4 Mar 2007 15:38:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Mar 2007 15:38:30 -0000 Authentication-Results: pb1.pair.com header.from=helly@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=helly@php.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain php.net from 85.214.94.56 cause and error) X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 85.214.94.56 aixcept.net Received: from [85.214.94.56] ([85.214.94.56:59668] helo=h1149922.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D8/34-08661-3F7EAE54 for ; Sun, 04 Mar 2007 10:38:29 -0500 Received: from [192.168.1.3] (dslb-084-063-021-112.pools.arcor-ip.net [84.63.21.112]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by h1149922.serverkompetenz.net (Postfix) with ESMTP id 0CD0B1B350F; Sun, 4 Mar 2007 16:38:25 +0100 (CET) Date: Sun, 4 Mar 2007 16:38:38 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <592868326.20070304163838@marcus-boerger.de> To: Pierre CC: kingwez@gmail.com, Arnold Daniels , In-Reply-To: References: <45E33990.8030806@adaniels.nl> <1331353216.20070226232944@marcus-boerger.de> <45E37D05.5040000@adaniels.nl> <408821909.20070303232323@marcus-boerger.de> <1508893792.20070304144812@marcus-boerger.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] suggestion SplFileInfo From: helly@php.net (Marcus Boerger) Hello Pierre, Sunday, March 4, 2007, 3:29:06 PM, you wrote: >> > It may be more useful to add streams support to our glob functions. >> > But it can bring more troubles than expected. I did not elaborate on this really. So let me do that now. If we were going this way we would need to always overwrite the native glob implementation which we don't do right now. The reason being that we actually prefer to use the native implementation. Which should also be faster as a side effect. Another thing is that doing so would only make the glob implementation itself profit from this. Providing the other way makes anything profit from glob support. We might even think of adding support for opening files through glob:// by having it open the first returned file when used for file opening. >> 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. In the same way as noted above a filter implementation would mean to have php come with an implementation of glob which we currently do not always have. Damn, it apprears we have different taste :-) Best regards, Marcus