[bug #59276] [PATCH] #include "config.h" before <stdio.h>

[Ingo Schwarze]

Follow-up Comment #7, bug #59276 (project groff):

Re: comment #6

Thanks, Dave, for noting that.

I decided to not waste my time replying to gnulib because:

1. They did not reply to the observation that their tests are wrong because
they assume that __restrict, if available, is the same as "restrict", which is
not guaranteed by the C standard.

2. They did not reply to the observation that their stdio.h violates the C++
standard.

3. They did not reply to the concern that gnulib actively and silently
disables security features, even on GNU/Linux.

So, they are clearly not interested, neither in standard conformance and
correctness nor in security.

It seems rather silly to me that we have to include "config.h" even in files
that don't need any portability help in the first place because they are
already completely portable on their own, in particular since the only reason
for that requirement is that gnulib itself violates standards...  In that
sense, gnulib causes more portability problems than it solves.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59276>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/