Xref: utzoo alt.msdos.programmer:610 comp.sys.ibm.pc:37322
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!netnews.engin.umich.edu!caen.engin.umich.edu!ejd
From: ejd@caen.engin.umich.edu (Edward J Driscoll)
Newsgroups: alt.msdos.programmer,comp.sys.ibm.pc
Subject: Re: Turbo C wildcard expansion
Message-ID: <468efc2a.103f1@palm.engin.umich.edu>
Date: 31 Oct 89 15:56:00 GMT
References: <3574@gouda.quad.com> <89302.005130CMH117@PSUVM.BITNET>
Reply-To: ejd@caen.engin.umich.edu (Edward J Driscoll)
Followup-To: alt.msdos.programmer
Organization: The University of Michigan, College of Enginering
Lines: 25

In article <89302.005130CMH117@PSUVM.BITNET> CMH117@PSUVM.BITNET 
(Charles Hannum) writes:
>ARGH!  That has to be some of the most convoluted code I have ever seen!  If
>you only have 1 statement in a block (an IF or ELSE clause, for example), there
>is *NO* reason to include begin and end-block braces!  It just makes the code
>longer and harder to read.
>

There's no *technical* reason.  It might make it harder for you to 
read, but others might find it easier to read (I, for one, appreciate
the parallel structure it gives to ALL the if statements).  It
certainly makes it less likely that you'll add in statements later
and forget to block them off with braces.  I do this all the time
to add in debugging code, and typing in the braces ahead of time
saves a lot of extra mental processing.  I'd say it's more a matter
of taste and style than a never-to-be-violated rule.

>Not being mean, but I like short and concise.
                     ^^^^^^
And I like braces that make it blatantly obvious which
statements are in the block.  See what I mean?
-- 
Ed Driscoll
The University of Michigan
ejd@caen.engin.umich.edu