From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 28023@debbugs.gnu.org, michael.albinus@gmx.de
Subject: bug#28023: fix make-temp-file race on local host
Date: Sat, 12 Aug 2017 19:52:46 +0300 [thread overview]
Message-ID: <83mv74iv8h.fsf@gnu.org> (raw)
In-Reply-To: <269e192f-15d8-4625-bbf0-ca11fb66edcc@cs.ucla.edu> (message from Paul Eggert on Sat, 12 Aug 2017 09:25:37 -0700)
> Cc: michael.albinus@gmx.de, 28023@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 12 Aug 2017 09:25:37 -0700
>
> I was following the lead of names like lread--substitute-command-keys,
> print--preprocess, and thread--blocker, all low-level C functions whose first
> part identifies which C module they're in. Although I see that the "-internal"
> suffix is more popular for this sort of thing, isn't that a revenant of the old
> days, before we instituted the convention of using PREFIX--NAME for private
> names? Or is the "-internal" suffix a separate naming convention, used by both
> Lisp and C code, that has a different semantics from PREFIX--NAME? If so, it
> would be nice to have advice somewhere as to when to use the -internal suffix vs
> when to use PREFIX--NAME.
I think the prefix that comes from the file where the function is
defined is more of a Lisp convention, and the -internal convention is
more for C implementations.
next prev parent reply other threads:[~2017-08-12 16:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 5:38 bug#28023: fix make-temp-file race on local host Paul Eggert
2017-08-09 6:51 ` Michael Albinus
2017-08-09 9:22 ` Paul Eggert
2017-08-09 11:21 ` Michael Albinus
2017-08-13 7:21 ` Paul Eggert
2017-08-12 10:35 ` Michael Albinus
2017-08-12 15:55 ` Paul Eggert
2017-08-12 16:09 ` Eli Zaretskii
2017-08-12 16:25 ` Paul Eggert
2017-08-12 16:52 ` Eli Zaretskii [this message]
2017-08-12 17:57 ` Paul Eggert
2017-08-12 18:07 ` Eli Zaretskii
2017-08-12 17:51 ` Michael Albinus
2017-08-09 16:05 ` Eli Zaretskii
2017-08-09 18:47 ` Paul Eggert
2017-08-09 19:09 ` Eli Zaretskii
2017-08-09 23:36 ` Paul Eggert
2017-08-10 15:35 ` Eli Zaretskii
2017-08-10 22:24 ` Paul Eggert
2017-08-11 6:21 ` Eli Zaretskii
2017-08-11 7:44 ` Paul Eggert
2017-08-11 8:03 ` Eli Zaretskii
2017-08-12 8:31 ` Eli Zaretskii
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=83mv74iv8h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28023@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=michael.albinus@gmx.de \
/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).