Date: Mon, 4 Dec 2000 00:06:51 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Will Andrews <will@physics.purdue.edu> Cc: Will Andrews <will@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/make arch.c compat.c cond.c dir.c hash.c job.c job.h list.h lst.h main.c make.c make.h parse.c sprite.h suff.c targ.c var.c src/usr.bin/make/lst.lib lstAppend.c lstConcat.c lstDatum.c lstDeQueue.c lstDestroy.c lstDupl.c ... Message-ID: <Pine.BSF.4.21.0012040002320.956-100000@besplex.bde.org> In-Reply-To: <20001203071530.N559@puck.firepipe.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 Dec 2000, Will Andrews wrote: > On Sun, Dec 03, 2000 at 07:12:24PM +1100, Bruce Evans wrote: > > K&R support is one reason. There are also stylistic reasons. Programmers > > who believe in explicit casting of values returned by malloc(), like the > > author of make(1), may believe in explicit types for everything. > > Yeah, I'm sure it's good for stylistic reasons. It just serves to > confuse programmers used to using NULL. And actually, I've never seen > linked lists using anything besides NULL. But then again, I didn't look > at the queue(3) implementation. > > Where does it say this supports K&R? It uses __P(()). __P(()) is nonsense if K&R is not fully supported. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0012040002320.956-100000>