Mark Murray 16fc3635f7 Make NULL a (void*)0 whereever possible, and fix the warnings(-Werror) ... that this provokes. "Wherever possible" means "In the kernel OR NOT C++" (implying C). There are places where (void *) pointers are not valid, such as for function pointers, but in the special case of (void *)0, agreement settles on it being OK. Most of the fixes were NULL where an integer zero was needed; many of the fixes were NULL where ascii <nul> ('\0') was needed, and a few were just "other". Tested on: i386 sparc64		2004-03-05 08:10:19 +00:00
..
alpha
amd64	Change the syscall stub branch orders so that the static branch prediction	2004-02-22 02:11:39 +00:00
compat-43
db
gdtoa
gen	Make NULL a (void*)0 whereever possible, and fix the warnings(-Werror)	2004-03-05 08:10:19 +00:00
gmon
i386	Remove the code and an associated comment for gcc 1.x compatibility	2004-02-16 10:03:02 +00:00
ia64
include	Make the resolver(3) and many associated interfaces much more reentrant.	2004-02-25 21:03:46 +00:00
locale	Make consistent with the better written wcsrtombs function:	2004-02-27 15:03:22 +00:00
net	Make NULL a (void*)0 whereever possible, and fix the warnings(-Werror)	2004-03-05 08:10:19 +00:00
nls
posix1e
powerpc	makecontext lib call.	2004-03-02 06:22:24 +00:00
quad
regex
rpc	Make NULL a (void*)0 whereever possible, and fix the warnings(-Werror)	2004-03-05 08:10:19 +00:00
sparc64
stdio	If handed a file pointer we can't write to, set errno properly to EBADF	2004-03-02 19:43:51 +00:00
stdlib	Make return code in noarg case GNU-compatible	2004-03-03 08:29:00 +00:00
stdtime
string
sys	Document missing EFAULT errno value.	2004-03-03 14:51:11 +00:00
uuid
xdr
yp
Makefile