Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!shelby!csli!poser
From: poser@csli.Stanford.EDU (Bill Poser)
Newsgroups: comp.std.c
Subject: Re: observability
Message-ID: <10321@csli.Stanford.EDU>
Date: 9 Sep 89 22:09:54 GMT
References: <1237@gmdzi.UUCP> <10885@smoke.BRL.MIL> <242@ssp1.idca.tds.philips.nl> <10937@smoke.BRL.MIL> <1989Sep6.160709.4890@light.uucp> <1989Sep6.183349.2866@jarvis.csri.toronto.edu> <28946@news.Think.COM> <1989Sep8.091010.12450@gdt.bath.ac.uk>
Sender: poser@csli.Stanford.EDU (Bill Poser)
Reply-To: poser@csli.stanford.edu (Bill Poser)
Organization: Center for the Study of Language and Information, Stanford U.
Lines: 8

In article <1989Sep8.091010.12450@gdt.bath.ac.uk> exspes@gdr.bath.ac.uk (P E Smee) writes:
>one might ask why you would want to write a chunk
>of code that has ZERO effect.

I sometimes do this during program development. I declare the data
structures and write the code that operates on them, leaving the i/o
to worry about later. I may want to compile at this point to check
for errors in the code.