Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!ukma!psuvax1!eldalonde!mckulka From: mckulka@eldalonde.endor.cs.psu.edu (Christopher Mc Kulka) Newsgroups: comp.lang.c Subject: Re: One more point regarding = and == (more flamage) Message-ID: Date: 22 Mar 91 22:29:39 GMT References: <13603@helios.TAMU.EDU> <3182@inews.intel.com> Sender: news@cs.psu.edu (Usenet) Organization: Penn State Computer Science Lines: 31 Nntp-Posting-Host: eldalonde.endor.cs.psu.edu In article <3182@inews.intel.com> bhoughto@pima.intel.com (Blair P. Houghton) writes: [STUFF DELETED] > /* mommy: please hold my hand */ > while ((*foo++ = *bar++) != 0) > >Basically, if you're worth the meager pittance they direct-deposit >into your debt with the Company Store, the comments will have >existed long before you wrote the code. Put those in, and make >them accurate, and it doesn't matter how much the code obfuscates. > >It's called top-down design, and involves _thinking_ before >you start making mistakes. Ahhh, it must be perfect in a perfect world where people do not make mistakes by *ACCIDENT*. Have you never missed an '=' or slipped in a ';' instead of a ',', or etc. Last time I checked I usually found mistakes after *thinking* I did not make any. Chris PS - If you have discovered a tonic that makes it possible to write programs larger than "Hello, world." correctly the first time, PLEASE let the rest of us know about it. We can *bury* Japan in a year. -- Just say *NO* to software patents & look-and-feel lawsuits. Try competition. If God had intended man to smoke he would have set him on fire. There are two ways to write an error-free program. Only the third works. Chris McKulka (mckulka@bree.endor.cs.psu.edu)