GNU bug report logs - #34849
Compilation issues with g++ on some files

Previous Next

Full log

Message #33 received at 34849 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Eli Zaretskii <eliz <at> gnu.org>, rms <at> gnu.org
Cc: 34849 <at> debbugs.gnu.org, agrambot <at> gmail.com
Subject: Re: bug#34849: Compilation issues with g++ on some files
Date: Tue, 19 Mar 2019 19:12:24 -0700

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.