Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51606 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34117 invoked from network); 7 Mar 2011 21:09:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Mar 2011 21:09:47 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.173 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.173 smtp173.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.173] ([67.192.241.173:50995] helo=smtp173.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E2/80-30054-A99457D4 for ; Mon, 07 Mar 2011 16:09:47 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id DD29A2582E7; Mon, 7 Mar 2011 16:09:43 -0500 (EST) X-Virus-Scanned: OK Received: by smtp7.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 62F052580ED; Mon, 7 Mar 2011 16:09:43 -0500 (EST) Message-ID: <4D754997.5080704@sugarcrm.com> Date: Mon, 07 Mar 2011 13:09:43 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.14) Gecko/20110221 Thunderbird/3.1.8 MIME-Version: 1.0 To: Pierre Joye CC: "internals@lists.php.net" References: <4D7431C3.10405@sugarcrm.com> <4D74A8FD.3020102@sugarcrm.com> <4D74AB3C.8040702@sugarcrm.com> <4D751AC2.3030800@sugarcrm.com> <4D7535E2.5040007@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] file streams & metadata From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > No I don't. But I'm telling you that what you propose is incomplete > and bad, to start with. Incomplete - yes. If we only implemented things that are "complete" in the sense you require, we would have no file operations in PHP at all - after all, we don't have support for reparse points and NTFS ACLs in file functions now, so by your logic they shouldn't be implemented until we design filesystem layer that allows to do it. Until then, PHP is better without any filesystem support at all. I don't see how it makes any sense. >> But again vfsStream example shows it will be useful not only for myself but >> for many others. Your argument is that since it doesn't cover some fringe >> case which nobody currently uses > > You are not everybody, nor is your projects, sorry. Come on, you know vfsStream is not my project and the problem is real. If you have proof that any of your counterexamples are widely used and streams are completely useless as filesystem layer without support for reparse points or NTFS ACLs - bring examples. Tell me which applications require them. Tell me how you unit-test them now and how you want to improve it. Without it, what I see is shooting down a good proposal because you can vaguely think of imagined better solution which nobody is going ever to design and implement. The result is we get no improvement at all. How is that any better? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227