From: Luke Lee <luke.yx.lee@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: contovob@tcd.ie, chenzhiwei03@kuaishou.com, emacs-devel@gnu.org
Subject: Re: master 87e7390: * lisp/progmodes/hideif.el: update for new C++ standards and extensions
Date: Thu, 03 Jun 2021 17:10:42 +0800 [thread overview]
Message-ID: <87sg1zpb3h.fsf@gmail.com> (raw)
In-Reply-To: <834kefxxgs.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 03 Jun 2021 09:40:19 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>
> How about making hideif.el capable of running a GCC command such as
> above automatically, and using the output to find which macros should
> be defined and which shouldn't?
> [...]
Yes, actually that was in my TODO list including the nesting recursive
#include process; however that might take a long time to run for any
decent project. The most important part is to set a configurable inclusion
path list to search, which also serves for GCC's "-I" arguments if it's
going to be executed automatically.
>
> As another "btw", we have cpp.el which provides a similar
> functionality; perhaps hideif.el could learn something from there?
Okay, I will take a look, meanwhile if you have a more specific item for
me to look please let me know. Thanks.
Best regards,
Luke Lee
next prev parent reply other threads:[~2021-06-03 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210602123045.16251.72470@vcs0.savannah.gnu.org>
[not found] ` <20210602123047.2969E209AA@vcs0.savannah.gnu.org>
2021-06-02 15:19 ` master 87e7390: * lisp/progmodes/hideif.el: update for new C++ standards and extensions Basil L. Contovounesios
2021-06-03 2:50 ` Zhiwei Chen
2021-06-03 3:38 ` Luke Lee
2021-06-03 6:40 ` Eli Zaretskii
2021-06-03 9:10 ` Luke Lee [this message]
2021-06-03 10:52 ` Eli Zaretskii
2021-06-03 3:19 ` Luke Lee
2021-06-03 6: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=87sg1zpb3h.fsf@gmail.com \
--to=luke.yx.lee@gmail.com \
--cc=chenzhiwei03@kuaishou.com \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).