From: xenodasein--- via "Emacs development discussions." <emacs-devel@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: "xenodasein--- viaEmacs development discussions."
<emacs-devel@gnu.org>, Richard Stallman <rms@gnu.org>,
Eli Zaretskii <eliz@gnu.org>,
pappasbrent@knights.ucf.edu
Subject: Re: Thoughts on replacing macros with static inline functions
Date: Fri, 18 Nov 2022 07:32:39 +0100 (CET) [thread overview]
Message-ID: <NH8R65Z--3-9@tutanota.de> (raw)
In-Reply-To: <87leo8eq0y.fsf@yahoo.com>
Nov 18, 2022, 06:27 by luangruo@yahoo.com:
> xenodasein--- via "Emacs development discussions." <emacs-devel@gnu.org>
> writes:
>
>> Why do you not consider __attribute__((always_inline)) an improvement
>> over macros where applicable?
>>
>
> And exactly where is __attribute__((always_inline)) present? Only on
> GCC, right? What about Sun C, and other C99 compilers?
>
> And how is an additional function an improvement over extremely trivial
> macros, like these:
>
> #define XM_DRAG_REASON(originator, code) ((code) | ((originator) << 7))
> #define XM_DRAG_REASON_ORIGINATOR(reason) (((reason) & 0x80) ? 1 : 0)
> #define XM_DRAG_REASON_CODE(reason) ((reason) & 0x7f)
>
> ?
>
Lookup why functions are considered an improvement over macros.
As for compiler support, I bet the time spent debugging where there is
support is going to dwarf where isn't, so trade-off is clear.
next prev parent reply other threads:[~2022-11-18 6:32 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. [this message]
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
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=NH8R65Z--3-9@tutanota.de \
--to=emacs-devel@gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--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).