From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: file-equal-p
Date: Thu, 16 Feb 2023 14:42:49 +0200 [thread overview]
Message-ID: <83wn4h3ho6.fsf@gnu.org> (raw)
In-Reply-To: <87pma9pz5v.fsf@yahoo.com> (message from Po Lu on Thu, 16 Feb 2023 20:34:04 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 16 Feb 2023 20:34:04 +0800
>
> 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 don't know, but punishing everyone for the benefit of a single OS
sounds wrong to me.
> It will otherwise result in file-attributes being called two more times
> on the system being tested against.
Not if you call file-attributes once and store the results in local
variables.
next prev parent reply other threads:[~2023-02-16 12:42 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 ` file-equal-p Po Lu
2023-02-16 12:42 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wn4h3ho6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.