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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
