From mboxrd@z Thu Jan 1 00:00:00 1970 From: ron@ronnatalie.com (Ron Natalie) Date: Thu, 22 Mar 2018 12:22:06 -0400 Subject: [TUHS] Comments in early Unix systems In-Reply-To: References: <20180321141753.25C4418C088@mercury.lcs.mit.edu> <6c6699c0-15db-604a-181c-7dad282599e1@kilonet.net> <20180321202810.GA6280@minnie.tuhs.org> <20180322012720.GN9739@mcvoy.com> Message-ID: <01d401d3c1f9$ebd18270$c3748750$@ronnatalie.com> > i.e. repeating anything i can see from the code (like “returns void”) tells me nothing. It's right up there with using #defines for silly things like #define FOUR 4 Great. What doe this tell me that the literal 4 doesn't. It's a matter of time until someone says #define FOUR 5 I actually found some code in use that had #define notdef 1 in it. I about went through the roof. Frankly, I have immense distaste for the definition NULL. Especially those implementations that try to fix it by introducing a spurious cast on it.