Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!ukma!rutgers!att!ihlpb!nevin1 From: nevin1@ihlpb.ATT.COM (Liber) Newsgroups: comp.lang.c Subject: Re: fortran to C converter Message-ID: <10371@ihlpb.ATT.COM> Date: 28 Apr 89 23:31:58 GMT References: <9244@alice.UUCP> <12716@lanl.gov> Reply-To: nevin1@ihlpb.UUCP (55528-Liber,N.J.) Organization: AT&T Bell Laboratories - Naperville, Illinois Lines: 31 In article <12716@lanl.gov> jlg@lanl.gov (Jim Giles) writes: >Most people put _one_ statement per line, No. Most people put AT MOST one statement per line. Many times, due to indentation, long variable names, etc., it is not possible to put a whole statement on just one line. Heck, even your beloved FORTRAN allows you to split lines (a minus sugn in the sixth column, I believe). >so the use of _both_ semicolon and carriage return as statement terminators >seems redundant. That's why carriage returns AREN'T statement terminators. >Why does C choose to ignore the "wrong" one? Using carriage returns as statement terminators leads to much trickier rules for line continuation. For example: is x = 1 -y one statement or two? It's not obvious which should be better (please, let's NOT debate it). [insert Sousa march here, and roll the credits :-)] -- _ __ NEVIN ":-)" LIBER nevin1@ihlpb.ATT.COM (312) 979-4751 IH 4F-410 ' ) ) "I will not be pushed, filed, stamped, indexed, / / _ , __o ____ briefed, debriefed or numbered! My life is my own!" / (_