From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: eggert@cs.ucla.edu, rms@gnu.org, 34849@debbugs.gnu.org
Subject: bug#34849: Compilation issues with g++ on some files
Date: Wed, 20 Mar 2019 09:05:14 +0200 [thread overview]
Message-ID: <8336nit49h.fsf@gnu.org> (raw)
In-Reply-To: <87wokunkti.fsf@gmail.com> (message from Alex on Wed, 20 Mar 2019 00:04:09 -0600)
> From: Alex <agrambot@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org, 34849@debbugs.gnu.org
> Date: Wed, 20 Mar 2019 00:04:09 -0600
>
> > https://lists.gnu.org/r/bug-gnulib/2019-03/msg00064.html
>
> My problem there was that lisp.h includes verify.h, so I figure it would
> have been better to either fix it in upstream (which got shot down) or
> wrap the single include in extern "C++" rather than wrap most of lisp.h
> in extern "C".
Why is it a problem to wrap most or all of lisp.h in extern "C"? Most
of your system headers do that already.
next prev parent reply other threads:[~2019-03-20 7:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 21:12 bug#34849: Compilation issues with g++ on some files Alex
2019-03-17 5:22 ` Alex
2019-03-18 1:47 ` Richard Stallman
2019-03-18 16:18 ` Alex
2019-03-19 2:24 ` Richard Stallman
2019-03-19 2:37 ` Paul Eggert
2019-03-19 4:45 ` Alex
2019-03-19 7:33 ` Eli Zaretskii
2019-03-20 2:12 ` Paul Eggert
2019-03-20 6:04 ` Alex
2019-03-20 7:05 ` Eli Zaretskii [this message]
2019-03-20 6:38 ` Eli Zaretskii
2019-03-20 2:31 ` Richard Stallman
2019-03-20 6:53 ` Eli Zaretskii
2019-03-21 2:09 ` Richard Stallman
2019-03-20 2:32 ` Richard Stallman
2019-03-20 10:53 ` Dmitry Gutov
2019-03-21 2:10 ` Richard Stallman
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=8336nit49h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34849@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=rms@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).