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: <3BAFC4A8.1090303@likai.net> Date: Mon, 24 Sep 2001 19:41:28 -0400 From: Li-Kai Liu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20010913 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [PATCH] ls & "magic" cygdrive dir (was: RE: cygdrive stuff) References: <3BAFBF02 DOT 4050809 AT likai DOT net> <100a01c1454f$bbcdbc80$0200a8c0 AT lifelesswks> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Robert Collins wrote: >----- 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 > however i am eager, i must agree with you on "one-step-at-a-time" approach. i know i have a tendency to get greedy and slurp a big chunk at once, but at the same time i also fear that any addition to (or more reliance on) the current unorthodox way fhandler works would also make the transition more difficult. liulk -- 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/