Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!uxc.cso.uiuc.edu!tank!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.lang.c
Subject: Re: LINT won't do your debugging for you
Message-ID: <3588@cps3xx.UUCP>
Date: 29 Jun 89 15:07:51 GMT
References: <713@srhqla.SR.COM>
Organization: Engineering, Michigan State U., E. Lansing MI
Lines: 18

in article <713@srhqla.SR.COM>, tcm@srhqla.SR.COM (Tim Meighan) says:
> 
> 1. There is rarely, if ever, a case when it would be reasonable for a
>    program to contain an if() statement that, when evaluated as true,
>    does absolutely nothing.  (In other words, simply fall through to
>    the code to be executed when the if() is false.)

When implementing some very low level code in C under MSDOS, an if
with a null body provides a very handy slight delay. Example: after
sending the address to the CMOS RAM on an AT, you need a slight pause on
a fast machine to then read or write its contents.

Unfortunately, alot of compilers optimize it out.

John H. Lawitzke           UUCP: Work: ...uunet!frith!dale1!jhl
Dale Computer Corp., R&D         Home  ...uunet!frith!ipecac!jhl
2367 Science Parkway       Internet:   jhl@frith.egr.msu.edu
Okemos, MI, 48864                             [35.8.8.108]