Branko Čibej <br...@wandisco.com> writes: > Sideline: *IF* we, as a community, agree to do this, then: (a) the rule > should be documented in HACKING, and (b) there should be a '#define > NULLPTR ((void*)0)' or reasonable facsimile in either svn_types.h or > svn_private_config.h. I really do not want to see '(char*)NULL' all over > the place. That's ... unsightly.
That would be incompatible with C++ since (void*) doesn't automatically convert to (char*) by default. I'd like to avoid such incompatibilities because I'd like to be able to use a C++ compiler at some point to catch things like enum mismatches. I suppose we could have NULLCHARPTR for variadic functions expecting (char*) which is the common case. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
