home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usna!faculty!baldwin
- From: baldwin@csservera.scs.usna.navy.mil (J.D. Baldwin)
- Newsgroups: comp.lang.c
- Subject: Re: The Correct Way To Write C if-Statements
- Message-ID: <BALDWIN.92Nov6131641@csservera.scs.usna.navy.mil>
- Date: 6 Nov 92 17:16:41 GMT
- References: <140742@lll-winken.LLNL.GOV>
- Sender: news@usna.NAVY.MIL
- Organization: Comp. Sci. Dep't., U.S. Naval Academy, Annapolis, MD
- Lines: 25
- In-reply-to: booloo@framsparc.ocf.llnl.gov's message of 05 Nov 92 18:49:33 -0400
-
- In article <140742@lll-winken.LLNL.GOV> booloo@framsparc.ocf.llnl.gov
- (Mark Boolootian) writes:
- >The following piece was written by Jim Minton, an aspiring C programmer.
- >I convinced him to let me post it to the net. Happy reading and flames
- >to /nev/dull...
- >
- > The Correct Way To Write C if-Statements
- > by
- > Jim Minton
-
- Well, *I* thought it was damn funny and true besides. I'm distribut-
- ing it to my students with the caveat that if they ever mix cases in
- their identifiers the way you do, I will hit them in the head with a
- baseball bat. HARD.
-
- Other than that, I think it's perfect. (Well, almost: I'm a
- 3-space-indent man, myself, but I don't advocate the actual
- imprisonment and torture of those who disagree with me by only one
- space.)
- --
- From the catapult of: |+| "If anyone disagrees with anything I
- _,_ J. D. Baldwin, Comp Sci Dept|+| say, I am quite prepared not only to
- _|70|___:::)=}- U.S. Naval Academy|+| retract it, but also to deny under
- \ / baldwin@usna.navy.mil |+| oath that I ever said it." --T. Lehrer
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-