From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org
Cc: 34849@debbugs.gnu.org, agrambot@gmail.com
Subject: bug#34849: Compilation issues with g++ on some files
Date: Tue, 19 Mar 2019 19:12:24 -0700 [thread overview]
Message-ID: <942e9a7c-c355-b199-fd88-861664783db4@cs.ucla.edu> (raw)
In-Reply-To: <838sxbuxn5.fsf@gnu.org>
Eli Zaretskii wrote:
> I believe the intent was to make the existing code be compilable with
> a C++ compiler without introducing any C++ code per se.
Although that may have been the intent, the downside is that a reasonable amount
of work and testing would have to be done to support it. On the Gnulib side
we've had some skepticism that this would be worth the hassle; see:
https://lists.gnu.org/r/bug-gnulib/2019-03/msg00060.html
Especially since there is a disciplined way of using the code that (at least for
Alex's need) appears to work well enough; see:
https://lists.gnu.org/r/bug-gnulib/2019-03/msg00064.html
> many/most of the toolkits and packages we'd
> like to use or be compatible with are written in C++ (HarfBuzz is a
> good recent example)
Sure, but as you mentioned HarfBuzz has a C API, and we needn't tweak or revamp
Emacs's C code in order to use HarfBuzz. In my experiences toolkits with a C++
API but without a C API tend to be less flexible and more of a hassle for C code
to interface to, and it's not clear we should spend much time catering to them.
next prev parent reply other threads:[~2019-03-20 2:12 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 [this message]
2019-03-20 6:04 ` Alex
2019-03-20 7:05 ` Eli Zaretskii
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=942e9a7c-c355-b199-fd88-861664783db4@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=34849@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=eliz@gnu.org \
--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).