From owner-freebsd-chat  Tue Feb  4 11:33:59 1997
Return-Path: <owner-chat>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA07061
          for chat-outgoing; Tue, 4 Feb 1997 11:33:59 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA07056
          for <chat@freebsd.org>; Tue, 4 Feb 1997 11:33:53 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA28784; Tue, 4 Feb 1997 12:33:39 -0700 (MST)
Date: Tue, 4 Feb 1997 12:33:39 -0700 (MST)
Message-Id: <199702041933.MAA28784@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Adam David <adam@veda.is>
Cc: nate@mt.sri.com (Nate Williams), chat@freebsd.org
Subject: Re: cvs commit: CVSROOT avail
In-Reply-To: <199702041941.TAA11400@veda.is>
References: <199702041559.IAA27474@rocky.mt.sri.com>
	<199702041941.TAA11400@veda.is>
Sender: owner-chat@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

[ moved to chat, as we're now discussing religion ]

> > > for(...)
> > >    ;
> > > 
> > > where it otherwise is very easy to miss the ;
> > 
> > Then do this:
> > 
> > for(...)
> >     continue;
> > 
> > Much more obvious what you are doing.
> 
> I beg to disagree. The previous example is far clearer, since the empty
> statement stands out as empty rather than being a coincidental noop.

The empty statement stands out like a mistake IMHO.

> Use
> of 'continue' in this context suggests that a line was deleted or has yet
> to be inserted.

I say the exact opposite.  The continue line implies to me that it's
intentional, vs. the other way.

> Of course, style also favours inserting a space before the parenthesis.

True, but in this manner everyone I've spoken with tends to prefer the
former over the latter (continue vs. empty semi-colon).



Nate