Bruno Haible <br...@clisp.org> writes: > Therefore, I would be in favour of EITHER > * doing this when the community as a whole has adopted 'nullptr' in C, i.e. > this keyword is no longer something that is new to an average newcomer, > (even if that's only 10 years from now), > OR > * doing the change only in those places where it actually matters, that is, > in varargs argument lists.
I agree with this conclucsion -- and pending 1) above, I believe 2) is sufficient and I would argue that we should all generally continue to use NULL in all other cases than varargs because it is a well-known idiom. This may cause 1) above to never occur, which seems acceptable. This assumes there aren't other important use-cases for nullptr than varargs that aren't clear. Personally I don't believe consistency with C++ is important (usually this makes C code uglier and less idiomatic in my experience) but opinion may vary. /Simon
signature.asc
Description: PGP signature
