From: Andreas Schwab <schwab@suse.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
cygwin@cygwin.com, henman@it.to-be.co.jp, emacs-devel@gnu.org
Subject: Re: New platform independent problem
Date: Fri, 20 Jan 2006 22:24:29 +0100 [thread overview]
Message-ID: <jeoe267fua.fsf@sykes.suse.de> (raw)
In-Reply-To: <43D0F12A.4000202@byu.net> (Eric Blake's message of "Fri, 20 Jan 2006 07:18:18 -0700")
Eric Blake <ebb9@byu.net> writes:
> What platforms use d_ino==0 to mean an empty entry, rather than an entry
> where st_ino must be checked?
This is traditional Unix behaviour. The original dirent structure (which
was actually struct direct from <sys/dir.h>) directly matched the contents
of the directory file on disk, and an entry was deleted by setting d_ino
to zero. Modern implementations of the dirent functions hide this detail
from the user and never return entries with d_ino == 0 any more.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-01-20 21:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 5:47 New platform independent problem djh
2006-01-20 11:08 ` Eli Zaretskii
2006-01-20 12:25 ` Corinna Vinschen
2006-01-20 13:59 ` Eric Blake
2006-01-20 14:14 ` Corinna Vinschen
2006-01-20 13:29 ` Igor Peshansky
2006-01-20 13:56 ` Eli Zaretskii
2006-01-20 14:18 ` Eric Blake
2006-01-20 16:48 ` Eli Zaretskii
2006-01-20 21:24 ` Andreas Schwab [this message]
2006-01-20 14:21 ` Corinna Vinschen
2006-01-27 20:45 ` Eli Zaretskii
2006-02-23 9:20 ` djh
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 17:01 Eric Blake
2006-01-20 17:22 ` Eli Zaretskii
2006-01-28 14:18 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jeoe267fua.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=cygwin@cygwin.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=henman@it.to-be.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).