From: "Julian Lohuis" <jlohuis@uni-osnabrueck.de>
To: gcc-help@gcc.gnu.org
Subject: dynamically parse c++-code-snipping from a plugin and skipping included files
Date: Thu, 09 Jun 2022 19:58:40 +0200 [thread overview]
Message-ID: <46d3-62a23500-6a7-643fe980@26385808> (raw)
next reply other threads:[~2022-06-09 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 17:58 Julian Lohuis [this message]
2022-06-09 18:23 ` dynamically parse c++-code-snippets " Julian Lohuis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46d3-62a23500-6a7-643fe980@26385808 \
--to=jlohuis@uni-osnabrueck.de \
--cc=gcc-help@gcc.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.
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).