Paul Eggert wrote:
> > It's still a bit early to do so, because it can trigger compilation errors
> > when people are not super careful
>
> Doesn't Gnulib's nullptr module fix the problems, whatever they are?
Yes, it does. But when - like here - people are using older C++ compilers,
or when I am
On 2023-09-04 18:04, Bruno Haible wrote:
It's still a bit early to do so, because it can trigger compilation errors
when people are not super careful
Doesn't Gnulib's nullptr module fix the problems, whatever they are?
(The URL you gave needs a GitHub login to view, which is a bit unfriendly.)
Paul Eggert wrote:
> I've been gradually switching code to use nullptr instead of NULL, so
> that GNU code won't be stuck in the 2010s.
It's still a bit early to do so, because it can trigger compilation errors
when people are not super careful (just saw this one today: [1]). It has
hurt me also
