Re: language design tradeoffs

raveling@Unify.com (Paul Raveling)
Mon, 21 Sep 1992 19:03:54 GMT

          From comp.compilers

Related articles
[23 earlier articles]
Re: language design tradeoffs tmb@arolla.idiap.ch (1992-09-20)
Re: language design tradeoffs eifrig@beanworld.cs.jhu.edu (1992-09-19)
Re: language design tradeoffs maxtal@extro.ucc.su.OZ.AU (1992-09-21)
Re: language design tradeoffs jch@rdg.dec.com (1992-09-21)
Re: language design tradeoffs nickh@CS.CMU.EDU (1992-09-21)
Re: language design tradeoffs jlg@cochiti.lanl.gov (1992-09-21)
Re: language design tradeoffs raveling@Unify.com (1992-09-21)
Re: language design tradeoffs alvin@eyepoint.com (1992-09-22)
Re: language design tradeoffs kcoppes@aardvark.den.mmc.com (1992-09-22)
Re: language design tradeoffs dmason@plg.uwaterloo.ca (1992-09-22)
Re: language design tradeoffs tmb@arolla.idiap.ch (1992-09-23)
Re: language design tradeoffs jlg@cochiti.lanl.gov (1992-09-23)
Re: language design tradeoffs bromage@mullauna.cs.mu.OZ.AU (1992-09-24)
[5 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers,comp.human-factors
From: raveling@Unify.com (Paul Raveling)
Organization: Unify Corporation (Sacramento)
Date: Mon, 21 Sep 1992 19:03:54 GMT
References: 92-09-048 92-09-093
Keywords: design, parse

jlg@cochiti.lanl.gov (Jim Giles) writes:
>3) The EOL character should be the statement terminator. [...]


rob@guinness.eng.ohio-state.edu (Rob Carriere) writes:
> Hm. Did whoever did that research take large mathematical expressions
> (which naturally translate to multi-line statements) into account? My
> single most common syntax error in FORTRAN and Matlab is forgetting the
> continuation marker on a multi-line statement.


It may well have taken that into account. Age-old research by Barry Boehm
and others concluded that most FORTRAN assignment statements were of the
form A = B, most of the rest were assignments to binary expressions -- A =
B + C. I don't trust my memory of actual numbers, but am fairly sure that
the first group accounted for >50% of all assignment statements, the 2nd
class was perhaps around 30%. Statements complex enough to need
continuation lines were a VERY small percentage of FORTRAN code, something
less than 5% I believe.


Based on Robert Firth's comments I'm inclined to think BCPL had the best
approach, treating EOL as a statement terminator if it makes sense
syntactically.
--
Paul Raveling
Raveling@Unify.com
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.