Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm list-help: list-post: Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-apps AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Sun, 25 Jun 2000 12:08:26 -0400 To: cygwin-apps AT sourceware DOT cygnus DOT com Subject: Re: Pending change to cygwin DLL and binmode/textmode musings Message-ID: <20000625120826.C790@cygnus.com> Mail-Followup-To: cygwin-apps AT sourceware DOT cygnus DOT com References: <20000624234013 DOT A29970 AT cygnus DOT com> <005601bfde69$c66fa0c0$f7c723cb AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <005601bfde69$c66fa0c0$f7c723cb@lifelesswks>; from robert.collins@itdomain.com.au on Sun, Jun 25, 2000 at 03:54:01PM +1000 On Sun, Jun 25, 2000 at 03:54:01PM +1000, Robert Collins wrote: >I like the idea of a database of files... that would mean less porting >issues, particularly with programs that act on files in common with other >tools. Personally, I don't like the thought of maintaining a list. I think we'll constantly be saying "Update your /etc/filemodes to the newest version". And, as the file grows larger it will take time to parse, slowing down every cygwin application. I guess we could get around that by setting some kind of flag in the executable but if we are going to do that then why not just record the filenames in the executable itself. I'd rather have the programs operate correctly without external dependencies. Of course, there is nothing stopping us from using both methods. cgf