From owner-freebsd-questions@FreeBSD.ORG Tue Oct 20 15:09:58 2009 Return-Path: Delivered-To: FreeBSD-Questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B4AC106568D for ; Tue, 20 Oct 2009 15:09:58 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.freebsd.org (Postfix) with ESMTP id 076DF8FC19 for ; Tue, 20 Oct 2009 15:09:57 +0000 (UTC) Received: (qmail 28528 invoked by uid 0); 20 Oct 2009 15:09:56 -0000 Received: from unknown (HELO Grumpy.DynDNS.org) (24.42.224.110) by smtp5.knology.net with SMTP; 20 Oct 2009 15:09:56 -0000 Received: by Grumpy.DynDNS.org (Postfix, from userid 928) id F3EAE28435; Tue, 20 Oct 2009 10:09:52 -0500 (CDT) Date: Tue, 20 Oct 2009 10:09:52 -0500 From: David Kelly To: FreeBSD-Questions@FreeBSD.org Message-ID: <20091020150952.GB42322@Grumpy.DynDNS.org> References: <20091019013337.GA9522@thought.org> <4ADBFDBA.6040702@pchotshots.com> <20091019170634.GA12371@thought.org> <4ADCAB4F.5040707@mahan.org> <20091020054241.ce4a38fe.freebsd@edvax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091020054241.ce4a38fe.freebsd@edvax.de> User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: need C help, passing char buffer[] by-value.... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD-Questions@FreeBSD.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2009 15:09:58 -0000 On Tue, Oct 20, 2009 at 05:42:41AM +0200, Polytropon wrote: > Just a little and quite formal side note: > > On Mon, 19 Oct 2009 11:09:19 -0700, Patrick Mahan wrote: > > while (*tp != '\0' && *tp++ != '<'); > > It's often a good choice, especially for increasing readability > of code, to code the "empty statement" on a line on its own (as > you usually put any statements on an own line for clarity), so > the reader doesn't accidentally take it as and "end of command" > notification, e. g. > > while(1) > ; > > instead of > > while(1); Agreed. I did exactly this in a code sample posted earlier in this thread. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.