From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Richard Stallman <rms@gnu.org>,
xenodasein@tutanota.de, Eli Zaretskii <eliz@gnu.org>,
pappasbrent@knights.ucf.edu, emacs-devel@gnu.org
Subject: Re: Thoughts on replacing macros with static inline functions
Date: Fri, 18 Nov 2022 17:16:00 +0100 [thread overview]
Message-ID: <87r0y0dyqy.fsf@web.de> (raw)
In-Reply-To: <jwvr0y0nwq1.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Why do you not consider __attribute__((always_inline)) an improvement
>> over macros where applicable?
>
> Can we drop this discussion. AFAIK all those who matter already
> explained clearly that we generally agree it's an improvement, but that
> it's not enough of an improvement to justify making the change just for
> the sake of it.
Thank you!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1121 bytes --]
next prev parent reply other threads:[~2022-11-18 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 18:05 Thoughts on replacing macros with static inline functions Brent Pappas
2022-11-15 12:45 ` Eli Zaretskii
2022-11-18 5:05 ` Richard Stallman
2022-11-18 6:19 ` xenodasein--- via Emacs development discussions.
2022-11-18 6:27 ` Po Lu
2022-11-18 6:32 ` xenodasein--- via Emacs development discussions.
2022-11-18 7:29 ` Po Lu
2022-11-18 8:34 ` Eli Zaretskii
2022-11-18 11:31 ` xenodasein--- via Emacs development discussions.
2022-11-18 11:43 ` Po Lu
2022-11-18 12:00 ` Eli Zaretskii
2022-11-18 6:59 ` tomas
2022-11-18 7:12 ` xenodasein--- via Emacs development discussions.
2022-11-18 14:53 ` Stefan Monnier
2022-11-18 16:16 ` Dr. Arne Babenhauserheide [this message]
2022-11-15 13:49 ` Po Lu
2022-11-15 15:54 ` xenodasein--- via Emacs development discussions.
2022-11-15 14:10 ` Stefan Monnier
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=87r0y0dyqy.fsf@web.de \
--to=arne_bab@web.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pappasbrent@knights.ucf.edu \
--cc=rms@gnu.org \
--cc=xenodasein@tutanota.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).