From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
Date:	Thu, 24 May 2001 19:52:42 +0200
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Add d_type member to struct dirent
Message-ID:	<20010524195242.A236@lauras.lt>
Mail-Followup-To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>,
	djgpp-workers AT delorie DOT com
References:	<20010523210505 DOT A478 AT lauras DOT lt> <Pine DOT SUN DOT 3 DOT 91 DOT 1010524084349 DOT 17472E-100000 AT is>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.15i
In-Reply-To:	<Pine.SUN.3.91.1010524084349.17472E-100000@is>; from eliz@is.elta.co.il on Thu, May 24, 2001 at 08:45:50AM +0300
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> > ...but in 99.9% cases __internal_readlink() will call just filelength()
> > to check for 510 bytes magic size. No open() at all in this case, and plain
> > filelength() is cheaper that stat(), isn't it?
> 
> ??? I don't have the latest CVS sources handy where I type this, but IIRC 
> filelength takes a handle, so __internal_readlink needs to open the file, 
> before it knows that it's 510 byte long.

What I forgot to tell is that __internal_readlink does findfirst() to
find out file size if it has path instead of the handle. Does my point
still hold true then?

Laurynas
 

- Raw text -