Re: Gnulib and nullptr

[Paul Eggert]

On 2/6/23 18:30, Paul Eggert wrote:
> 1. Since the nullptr issue affects C++ so much (something I wasn't aware 
> of until now), I'm inclined to rename the module from c-nullptr to 
> nullptr as was hinted earlier. It's not just C so the "c-" is a bit 
> misleading.
>
> 2. The issues you mentioned about C++ compilers possibly not supporting 
> nullptr seem to be serious enough that it seems that we should test the 
> C++ compiler at configure time, as we already test the C compiler. That 
> way we wouldn't have to worry whether our __cplusplus-related #ifdefs 
> are OK.

I installed the attached to try to address these issues. The third patch 
fixes some problems I ran into when using the first two on diffutils and 
groff. I pushed the diffutils change onto Savannah (but not groff of 
course). Comments welcome, as quite possibly there are further 
opportunities for improvement.

0001-nullptr-rename-from-c-nullptr.patch
Description: Text Data

0002-nullptr-test-for-C-nullptr-at-configure-time.patch
Description: Text Data

0003-nullptr-test-for-compilers-at-autoconf-time.patch
Description: Text Data