From: xenodasein--- via "Emacs development discussions." <emacs-devel@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Brent Pappas <pappasbrent@knights.ucf.edu>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Thoughts on replacing macros with static inline functions
Date: Tue, 15 Nov 2022 16:54:02 +0100 (CET) [thread overview]
Message-ID: <NGvzpHH--3-9@tutanota.de> (raw)
In-Reply-To: <87tu30fhut.fsf@yahoo.com>
Nov 15, 2022, 13:49 by luangruo@yahoo.com:
> Brent Pappas <pappasbrent@Knights.ucf.edu> writes:
>
>> Title: Thoughts on replacing macros with static inline functions
>> ...
>>
>>
> I find that rather ugly. PAD is an example of an extremely trivial
> expression that should really be a macro.
>
>> How interested would the Emacs community be in porting macros to functions?
>>
>
> Not very, in this case. That exact PAD macro is not only an idiom used
> throughout the Emacs X11 code, it is more-or-less an idiom of the entire
> X Window System, copied around and used extensively throughout the X
> sample server, Xlib, and C-language clients.
>
> In addition, we try to avoid undue changes to working code, so giving
> carte blanche to change macros to static functions is not something we
> really want to do. But if you want to do that to a few big, ugly,
> macros around an area in which you are making actual changes, please go
> ahead.
>
You answer in a tone that means you speak for everyone else, is this
intentional if so why?
next prev parent reply other threads:[~2022-11-15 15:54 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
2022-11-15 13:49 ` Po Lu
2022-11-15 15:54 ` xenodasein--- via Emacs development discussions. [this message]
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=NGvzpHH--3-9@tutanota.de \
--to=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=pappasbrent@knights.ucf.edu \
--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).