From: Eli Zaretskii <eliz@gnu.org>
Cc: cygwin@cygwin.com, henman@it.to-be.co.jp, emacs-devel@gnu.org
Subject: Re: New platform independent problem
Date: Fri, 20 Jan 2006 19:22:39 +0200 [thread overview]
Message-ID: <uk6curezk.fsf@gnu.org> (raw)
In-Reply-To: <012020061701.4999.43D11771000C3BE00000138722058861720A050E040D0C079D0A@comcast.net> (ericblake@comcast.net)
> From: ericblake@comcast.net (Eric Blake)
> Cc: cygwin@cygwin.com, henman@it.to-be.co.jp, emacs-devel@gnu.org
> Date: Fri, 20 Jan 2006 17:01:37 +0000
>
> > You could have a flag that, if set, will instruct readdir to do the
> > expensive processing. Applications that need the real inode will set
> > that flag.
>
> And then we would have to change applications to call this nonstandard
> entry point at the beginning of their program to set the flag.
Not necessarily, you could do that in a static constructor in a
Cygwin-specific source file, far from the application's sources, which
will remain unpolluted.
> As long as we are editing programs, we might as well teach them to
> respect a sentinel of -1 without having to resort to adding a
> nonstandard entry point.
I don't see how this is better: -1 is an arbitrarily picked value,
with no relation to any standard. Why should applications learn about
it?
next prev parent reply other threads:[~2006-01-20 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 17:01 New platform independent problem Eric Blake
2006-01-20 17:22 ` Eli Zaretskii [this message]
2006-01-28 14:18 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 5:47 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
2006-01-20 14:21 ` Corinna Vinschen
2006-01-27 20:45 ` Eli Zaretskii
2006-02-23 9:20 ` djh
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=uk6curezk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cygwin@cygwin.com \
--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).