Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!europa.asd.contel.com!sura.net!haven!uvaarpa!mcnc!ecsgate!ecsvax!uncw!session
From: session@uncw.UUCP (Zack C. Sessions)
Newsgroups: comp.lang.c
Subject: Re: _continue_ as NOP
Message-ID: <1023@uncw.UUCP>
Date: 27 Feb 91 20:05:16 GMT
References: <1991Feb22.181921.21478@inferno.peri.com>
Organization: Univ. of North Carolina at Wilmington
Lines: 29

shane@inferno.peri.com (Shane Bouslough) writes:

>Consider the following single statement while loop:

>	while ( actual work happens in here )
>		;

>I have seen _continue_ used to make the NOP semi-colon a
>little less invisible:

>	while ( actual work happens in here )
>		continue;

>What is the general consensus of this practice? Please praise,
>yawn, or flame at will.

I don't know what any accepted standard is, but my personal
preference in this type of construct is:

	while ( actual work happens in here ) ;
	next_statement;

I actually put the semi-colon on the while (or for()) on the
same line as the while (or for()). The next statement being flush
left with the previous line should be indication enough of the
structure of the code. (IMHO)

Zack Sessions
...!ecsvax!uncw!session