Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <426A4F68.3040506@byu.net> Date: Sat, 23 Apr 2005 07:36:40 -0600 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: support dirent.d_type References: <20050422170611 DOT GL16791 AT trixie DOT casa DOT cgf DOT cx> In-Reply-To: <20050422170611.GL16791@trixie.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Christopher Faylor on 4/22/2005 11:06 AM: > Actually, thanks but I don't think we want to go down this path. > > Properly implementing this field would introduce the same problems as > properly implementing d_ino. Doing this would mean adding too much > overhead to readdir. But there are a number of applications out there that behave more efficiently if d_ino/d_type ARE properly implemented. For example, both coreutils and findutils are smart enough to avoid extra [l]stat()s on systems with working d_type when traversing directories. You may find that properly implementing d_type slows down readdir() but speeds up applications. Most applications that use readdir() are doing so in the context of directory traversal, and have to do a followup stat or lstat to find out the type if readdir() doesn't tell them. - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCak9n84KuGfSFAYARAgVDAJ45iPUSGtUP4mqEqQoprPrhbHCXswCfVfQJ XyadNMn5xjFKlQxWYtzkq98= =M1zX -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/