From owner-cvs-all Thu Mar 7 14:31:10 2002 Delivered-To: cvs-all@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 7E57037B428; Thu, 7 Mar 2002 14:30:54 -0800 (PST) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.11.6/8.11.6) with UUCP id g27MUoH62797; Thu, 7 Mar 2002 22:30:50 GMT (envelope-from mark@grimreaper.grondar.za) Received: from grimreaper (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.2/8.12.2) with ESMTP id g27MRWRV017994; Thu, 7 Mar 2002 22:27:32 GMT (envelope-from mark@grimreaper.grondar.za) Message-Id: <200203072227.g27MRWRV017994@grimreaper.grondar.org> To: nate@yogotech.com (Nate Williams) Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/rwall rwall.c References: <15495.59008.192220.654176@caddis.yogotech.com> In-Reply-To: <15495.59008.192220.654176@caddis.yogotech.com> ; from Nate Williams "Thu, 07 Mar 2002 15:15:28 MST." Date: Thu, 07 Mar 2002 22:27:32 +0000 From: Mark Murray Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > void main(){printf("hello world\n");} > > > also produces correct code and runs, but creates problems during > > compiler and library upgrades. It his hard to read, and is > > unpredictable in silly ways. > > What problems (details)? Why it it hard to read? It is trivial to read > and understand. Who says printf is not a macro? What is the return value? void main() { printf("hello world\n"); } Is much easier to read, making the one liner "hard". (Trivial example, don't belabour this point). There is non-style(9) code in the tree that is much harder to read before it is style.9-ified. > > NO! I am not. If I wanted to do that, I'd do something dumbass like > > indent(1) all the code. > > It seems to me to be almost the same thing, but at least with indent, > bugs are introduced. :( I guess you mean "NOT introduced"? > *EVERYONE* likes well-written/safe code. Running it through lint and > fixing errors doesn't necessarily provide you with either feature. Huh? Fixing errors doesn't help make safe(r) code? M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message