From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lgustavo@codesourcery.com, petr.hluzin@gmail.com,
gdb@sourceware.org, macro@codesourcery.com
Subject: Re: Unreliable BFD caching heuristic
Date: Wed, 04 Dec 2013 15:54:00 -0000 [thread overview]
Message-ID: <87fvq8r4s5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83a9gh46qz.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 04 Dec 2013 05:47:32 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Luis> Thanks, but i don't think we would like to have windows-specific calls
Luis> in such a generic portion of code.
Eli> I don't understand: if you want to use inode numbers on Posix systems,
Eli> which requires a Unix-specific call, then why not use
Eli> GetFileInformationByHandle, which gives the Windows equivalent of the
Eli> inode? IOW, if you can have _real_ inodes on Windows, why risk the
Eli> fake ones?
FWIW it seems fine to me as well.
I'm sure one of our several existing portability mechanisms is suitable
for this task.
Tom
prev parent reply other threads:[~2013-12-04 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 17:39 Luis Machado
2013-11-21 17:58 ` Pedro Alves
2013-11-21 21:58 ` Tom Tromey
2013-11-23 12:14 ` Phi Debian
2013-11-25 17:45 ` Luis Machado
2013-11-25 18:07 ` Pedro Alves
2013-11-25 18:08 ` Maciej W. Rozycki
2013-11-25 18:21 ` Pedro Alves
2013-12-02 15:42 ` Tom Tromey
2013-12-03 15:28 ` Luis Machado
[not found] ` <CAC=yr6DRDsRLStnDNZW_2=0vOQY-oJHd55_nLUeb8Qetxo=yXw@mail.gmail.com>
2013-12-04 0:01 ` Luis Machado
2013-12-04 3:47 ` Eli Zaretskii
2013-12-04 15:54 ` Tom Tromey [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvq8r4s5.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=macro@codesourcery.com \
--cc=petr.hluzin@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox