** On 08/03/11 15:46, Matthew Weier O'Phinney wrote: > On 2011-03-08, Pierre Joye <pierre....@gmail.com> wrote: >> On Mon, Mar 7, 2011 at 10:49 PM, Ferenc Kovacs <i...@tyrael.hu> wrote: >> >>> From the sideline: >>> it's hard to belive that there are no one else with opinion on this matter. >>> I don't want to take sides because I don't have the necessary knowledge >>> about the matter, but maybe it would be a good idea to write an RFC, and and >>> maybe a POC, so we can see how intrusive would be the implementation. >>> and if there are more bystanders, then please make your voice heard. >>> Tyrael >> It is very easy to implement what Stas is asking. But that's not the >> question. The question is should we do it? And my point is that we >> should not do it like that, bad design, incomplete and limited >> support. > As a developer, in many cases I'd prefer something incomplete and limited in > support to nothing at all. I've been bitten by the same issue Stas describes, > and having a way to tie into touch and chmod in my stream wrappers would be > incredibly useful -- even if it won't work with _every_ stream. > /while I'd love to have a lovely fully working on all streams-types/platforms solution to make life easy, just having something in place would reduce the pain/workarounds i (and probably others) are having to use to a degree, and gives a starting point for future development. As long as whatever comes out is incomplete rather than broken/buggy then i can't see the problem with not waiting for a fully complete solution. "//A journey/ of a thousand miles begins with a /single step" + "Rome was not built in a day" That said i'm not really sure there is any obvious way to attack the shear number of FS/OS combo's that i've seen in existence... ///
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
