Re: if UNIX then USE_C ?? (was: Reasons for drop)

[rdh@sli.com (Robert D. Houk)]

In article <5563@crdgw1.crd.ge.com> kassover@jupiter.crd.ge.com (David Kassover) writes:

   Or even worse, I think, is the use of {} for many different kinds
   of block statements.  In Ada I end a loop with end loop;  I end
   an if with end if;

   In C, both of these things are delimited by {}.  Can anyone out
   there honestly say he's never got his braces tangled?  8-)
   (That's a pun, by the way)

Yeah, I've tangled up {}'s in C proggies. I've also put in lots of
"endif"s and just plain "end"s in Ada. And I've left ";"s out of both.
Overall, I prefer {}'s simply because they emphasize or make code blocks
stand out better when perusing the listing (to my way of thinking anyways)
[i.e., I look at "end if;" and want to see a meaningful source statement
at the same code-level as the originating "if" clause, not a tail-end of
something earlier. I don't know if that makes sense to anyone, but that's
the way I think...]

					-RDH
--
  "If you build a system                 RDH@SLI.COM  |	 uunet!sli!rdh
 that even a fool could use,             Robert D. Houk
   then only a fool                      Software Leverage, Inc.
 would want to use your system."         485 Massachusetts Avenue
        -Somebody-r-Other's Law          Arlington, Mass.  02174
                                         Office (617) 648-1414