Re: language design tradeoffs

macrakis@osf.org (Stavros Macrakis)
Tue, 15 Sep 1992 22:12:15 GMT

          From comp.compilers
Related articles
language design tradeoffs kotula@milli.cs.umn.edu (1992-09-07)
Re: language design tradeoffs torbenm@diku.dk (1992-09-08)
Re: language design tradeoffs nr@dynastar.Princeton.EDU (1992-09-09)
Re: language design tradeoffs raveling@Unify.com (1992-09-11)
Re: language design tradeoffs weberwu@inf.fu-berlin.de (1992-09-13)
Re: language design tradeoffs rob@guinness.eng.ohio-state.edu (1992-09-14)
Re: language design tradeoffs tmb@arolla.idiap.ch (1992-09-14)
Re: language design tradeoffs macrakis@osf.org (1992-09-15)
Re: language design tradeoffs jlg@cochiti.lanl.gov (1992-09-15)
Re: language design tradeoffs anw@maths.nott.ac.uk (1992-09-16)
Re: language design tradeoffs drw@euclid.mit.edu (1992-09-16)
Re: language design tradeoffs rob@guinness.eng.ohio-state.edu (1992-09-17)
Re: language design tradeoffs bromage@mullauna.cs.mu.OZ.AU (1992-09-17)
Re: language design tradeoffs jch@rdg.dec.com (1992-09-17)
[27 later articles]
| List of all articles for this month |
Newsgroups: comp.compilers,comp.human-factors
From: macrakis@osf.org (Stavros Macrakis)
Organization: OSF Research Institute
Date: Tue, 15 Sep 1992 22:12:15 GMT
Keywords: design
References: 92-09-048 92-09-070

rob@guinness.eng.ohio-state.edu (Rob Carriere) writes:


      In fact, I would argue that a language that requires coding that way has
      superior syntax to a do/od language, because of the well-known problem
      with the spelling of the terminators. Things like TNEMMOC, CNUF and NIGEB
      start looking OD rather quickly.


There are other possible conventions, as used in, e.g., Ada:


1) Use "end X" where X is the name of the opening delimiter, e.g. "end
      loop;", "end record;" etc.


2) Use "end X" where X is the name of the named unit (e.g. function,
      module, ...).


At first, I found it strange that the end delimiter should have a
"statement delimiter" afterwards, but in practice it looks quite
reasonable.


-s
--

Post a followup to this message

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