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

[kassover@jupiter.crd.ge.com (David Kassover)]

In article <204@puma.ge.com> jnixon@andrew.ATL.GE.COM (John F Nixon) writes:
>Sorry, you must be thinking of FORTRAN (e.g., DO 100 I = 1.10), not C.
>If c.l.a is going to be comparing languages, let's get them right.
>
No need to apologize, I *was* thinking of FORTRAN, specifically
that example, since we discussed it in particular.
 
But it is possible to make single character mistakes in C.
Just as bad, you can make single word mistakes in C, since there
are cases where things like semicolons and breaks are optional.

(Unless I misunderstand, or those options have been eliminated
since I read K&R.  If so, I apologise)

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)

FORTRAN is even worse:
 
	DO 100 I=1,10
	DO 100 J=1,10
	   .
	   .
	   .
100	CONTINUE
	   .
	   .
	   .
	GOTO 100

At least VAX FORTRAN provides an ENDDO and a DO WHILE