[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Test for getaddrinfo() broken on Tru64 UNIX 5.1
From: |
Jim Meyering |
Subject: |
Re: Test for getaddrinfo() broken on Tru64 UNIX 5.1 |
Date: |
Sat, 13 Oct 2007 22:23:10 +0200 |
Bruno Haible <address@hidden> wrote:
> Benoit SIGOURE wrote:
>> > 4) Don't use 0 to designate null pointers. That doesn't sit well with
>> > C++ compilers.
>>
>> s/C++/C/ right?
>
> Actually, neither C nor C++ compilers cry when you use 0 for NULL. It's only
> my personal preference.
I prefer to use NULL, too.
I've used sparse to help enforce the policy, but not recently:
http://git.kernel.org/?p=devel/sparse/sparse.git;a=summary
- Re: Test for getaddrinfo() broken on Tru64 UNIX 5.1, (continued)
- Re: Test for getaddrinfo() broken on Tru64 UNIX 5.1, Ben Pfaff, 2007/10/13
- Re: 0 vs. NULL (was: Re: Test for getaddrinfo() broken on Tru64 UNIX 5.1), Bruno Haible, 2007/10/13
- Re: 0 vs. NULL, Micah Cowan, 2007/10/13
- Re: 0 vs. NULL, Bruno Haible, 2007/10/13
- Re: 0 vs. NULL, Paul Eggert, 2007/10/15
- Re: 0 vs. NULL, Micah Cowan, 2007/10/15
- Re: Test for getaddrinfo() broken on Tru64 UNIX 5.1,
Jim Meyering <=
Re: Test for getaddrinfo() broken on Tru64 UNIX 5.1, Simon Josefsson, 2007/10/13
Re: Test for getaddrinfo() broken on Tru64 UNIX 5.1, Albert Chin, 2007/10/14