Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <100a01c1454f$bbcdbc80$0200a8c0@lifelesswks> From: "Robert Collins" To: "Li-Kai Liu" , "Ronald Landheer" , References: <3BAFBF02 DOT 4050809 AT likai DOT net> Subject: Re: [PATCH] ls & "magic" cygdrive dir (was: RE: cygdrive stuff) Date: Tue, 25 Sep 2001 09:22:08 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 24 Sep 2001 23:30:02.0494 (UTC) FILETIME=[D58359E0:01C14550] ----- Original Message ----- From: "Li-Kai Liu" > however, files and file systems are two different concepts! fhandler Corinna has already indicated that this is the desired end direction, with one class hierarchy for fs's and one for files. > apparently it is not the way it is right now in cygwin. :( Exactly. However making the readdir and opendir calls use objects and stop being hardcoded to win32 is a good step in the right direction. > to code the way i want them to. i'll genuinely code this thing if I know > that people like my idea and so it won't end up being hated and discarded. It won't end up being hated and discarded :]. I strongly suggest a one-step-at-a-time approach though: a series of small patches that make specific changes to get from here to there. Biting off too much is a common reason for architectural changes to fail. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/