From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: eggert@cs.ucla.edu, 34849@debbugs.gnu.org, agrambot@gmail.com
Subject: bug#34849: Compilation issues with g++ on some files
Date: Tue, 19 Mar 2019 09:33:02 +0200 [thread overview]
Message-ID: <838sxbuxn5.fsf@gnu.org> (raw)
In-Reply-To: <E1h64QM-0000T6-Fn@fencepost.gnu.org> (message from Richard Stallman on Mon, 18 Mar 2019 22:24:18 -0400)
> From: Richard Stallman <rms@gnu.org>
> Date: Mon, 18 Mar 2019 22:24:18 -0400
> Cc: eggert@cs.ucla.edu, 34849@debbugs.gnu.org
>
> 1. I don't want C++ code in the Emacs distribution. This isn't the sort
> of crucial thing that would override that general policy.
I believe the intent was to make the existing code be compilable with
a C++ compiler without introducing any C++ code per se.
My POV on this is that we should make Emacs buildable with as many
modern GUI toolkits as practically possible/reasonable, because it is
not clear which one(s) of them will remain workable and maintained in
the long run. And since 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), we should try making our sources be more
friendly to C++ compilers, as much as possible, because not every such
package has a C glue, like HarfBuzz does.
Therefore, if integration with Qt is reasonably possible, we should
not reject it outright. I understand the concerns regarding the
license, but we will need to revisit that when GPL's version is
advanced, and not sooner. Disabling support for a package that no
longer satisfies our requirements is relatively easy.
next prev parent reply other threads:[~2019-03-19 7:33 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 [this message]
2019-03-20 2:12 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838sxbuxn5.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.