Re: The semicolon habit (was: Q: Definition

"Dr A. N. Walker" <anw@maths.nottingham.ac.uk>
Tue, 16 May 1995 14:00:54 GMT

          From comp.compilers

Related articles
[3 earlier articles]
Re: The semicolon habit (was: Q: Definition lutz@KaPRE.COM (1995-05-11)
Re: The semicolon habit (was: Q: Definition sys3bga@doc.ntu.ac.uk (1995-05-05)
Re: The semicolon habit (was: Q: Definition stidev@gate.net (1995-05-09)
Re: The semicolon habit (was: Q: Definition plong@perf.com (1995-05-09)
Re: The semicolon habit (was: Q: Definition everettm@walters.East.Sun.COM (1995-05-11)
Re: The semicolon habit (was: Q: Definition schrod@iti.informatik.th-darmstadt.de (1995-05-12)
Re: The semicolon habit (was: Q: Definition anw@maths.nottingham.ac.uk (Dr A. N. Walker) (1995-05-16)
Re: The semicolon habit (was: Q: Definition cef@geodesic.com (Charles Fiterman) (1995-05-17)
Re: The semicolon habit (was: Q: Definition reid@HASKELL.SYSTEMSZ.CS.YALE.EDU (1995-05-16)
Re: The semicolon habit (was: Q: Definition jan@neuroinformatik.ruhr-uni-bochum.de (1995-06-24)
Re: The semicolon habit (was: Q: Definition tim@handel.Princeton.EDU (1995-06-24)
Re: The semicolon habit (was: Q: Definition bevan@cs.man.ac.uk (1995-06-30)
Re: The semicolon habit (was: Q: Definition cbloom@utxvms.cc.utexas.edu (1995-07-01)
[4 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
From: "Dr A. N. Walker" <anw@maths.nottingham.ac.uk>
Keywords: algol68, design, comment
Organization: Maths Dept., Nottingham University, UK.
References: 95-04-193 95-05-062
Date: Tue, 16 May 1995 14:00:54 GMT

our moderator comments:
>[Comment That's a good point, but what about Algol68's extremely overloaded
>punctuation that let you write if a then b else c fi as (a|b|c) ?
>tnemmoC -John]


What about it?


Firstly, allowing you to write "if ... fi" in an alternate form is
surely *under*loading. It allows the user to use "elegant variation" in
styles to make meanings clearer -- you can use, for example, vertically
aligned "if ... fi" for major blocks of code, horizontally aligned
"if ... fi" for key single-line code, and "(...)" for trivia that you
want to slip into place without drawing the reader's attention.


Secondly, the meat of your point [which ISTR you have made before]
is presumably that the *compiler* [and hence the reader] finds it quite
hard to tell whether a left parenthesis is meant to be "(", "[", "if",
"case" or "begin". But it doesn't matter! They are all brackets; and
that in itself is quite an insight for the reader -- one that many more
recent languages have failed to notice [or to exploit].


--
Andy Walker, Maths Dept., Nott'm Univ., UK.
anw@maths.nott.ac.uk


[Agreed, it's not important whether it's hard to compile, but it
seems to me that you could get some hard to find program errors by misplacing
a vertical bar and turning a case into an if or v.v. -John]
--


Post a followup to this message

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