[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: swarm of bugs in gnulib wrt restrict
|
From: |
Bruno Haible |
|
Subject: |
Re: swarm of bugs in gnulib wrt restrict |
|
Date: |
Sun, 25 Oct 2020 01:59:40 +0200 |
|
User-agent: |
KMail/5.1.3 (Linux/4.4.0-189-generic; KDE/5.18.0; x86_64; ; ) |
Paul Eggert wrote:
> > https://savannah.gnu.org/bugs/index.php?59276
>
> As I understand it, the problem here is that Gnulib-using C++ code can't use
> 'restrict' as an identifier.
No, that is not even the problem: The groff source code does not use 'restrict'
as an identifier, nowhere.
When I look at this recent commit of Ingo Schwarze [1], it seems the problem
was an incorrect use of Gnulib: Some source .cpp files did not have
#include <config.h>
as their first non-comment line. But this is a documented requirement for
packages that use Gnulib [2], since 2007.
Bruno
[1]
https://git.savannah.gnu.org/gitweb/?p=groff.git;a=commitdiff;h=fe121eeacd53c96105f23209b2c205f436f97359
[2] https://www.gnu.org/software/gnulib/manual/html_node/Source-changes.html