From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: file-equal-p
Date: Thu, 16 Feb 2023 20:34:04 +0800 [thread overview]
Message-ID: <87pma9pz5v.fsf@yahoo.com> (raw)
In-Reply-To: <83357596a0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 Feb 2023 13:52:23 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> It is still one more test, done for everyone.
Is file-equal-p a function called in particularly tight loops?
I think trying to optimize out a test against system-type is premature.
It will otherwise result in file-attributes being called two more times
on the system being tested against.
next prev parent reply other threads:[~2023-02-16 12:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a61es8fh.fsf.ref@yahoo.com>
2023-02-16 1:30 ` file-equal-p Po Lu
2023-02-16 8:18 ` file-equal-p Eli Zaretskii
2023-02-16 8:43 ` file-equal-p Po Lu
2023-02-16 8:57 ` file-equal-p Eli Zaretskii
2023-02-16 9:59 ` file-equal-p Po Lu
2023-02-16 11:52 ` file-equal-p Eli Zaretskii
2023-02-16 12:34 ` Po Lu [this message]
2023-02-16 12:42 ` file-equal-p Eli Zaretskii
2023-02-17 2:40 ` file-equal-p Po Lu
2023-02-17 6:26 ` file-equal-p Eli Zaretskii
2023-02-17 7:07 ` file-equal-p Po Lu
2023-02-17 8:32 ` file-equal-p Eli Zaretskii
2023-02-17 11:05 ` file-equal-p Po Lu
2023-02-16 9:15 ` file-equal-p Andreas Schwab
2023-02-16 9:58 ` file-equal-p Po Lu
2023-02-16 10:35 ` file-equal-p Michael Albinus
2023-02-16 12:35 ` file-equal-p Po Lu
2023-02-16 12:43 ` file-equal-p Eli Zaretskii
2023-02-17 4:50 ` file-equal-p Richard Stallman
2023-02-17 10:02 ` file-equal-p Andreas Schwab
2023-02-17 12:25 ` file-equal-p Eli Zaretskii
2023-02-17 12:45 ` file-equal-p tomas
2023-02-17 13:17 ` file-equal-p Andreas Schwab
2023-02-18 12:25 ` file-equal-p Eli Zaretskii
2023-02-18 14:04 ` file-equal-p Andreas Schwab
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=87pma9pz5v.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).