Re: The semicolon habit (was: Q: Definition

stidev@gate.net (Solution Technology)
Tue, 9 May 1995 11:27:06 GMT

          From comp.compilers

Related articles
Re: The semicolon habit (was: Q: Definition of a scripting lang.) schrod@iti.informatik.th-darmstadt.de (1995-04-28)
Re: The semicolon habit (was: Q: Definition lutz@KaPRE.COM (1995-04-28)
Re: The semicolon habit (was: Q: Definition lutz@KaPRE.COM (1995-05-09)
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)
[8 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
From: stidev@gate.net (Solution Technology)
Keywords: syntax, algol68, comment
Organization: Compilers Central
References: 95-04-193 95-05-027
Date: Tue, 9 May 1995 11:27:06 GMT

Mark Lutz (lutz@KaPRE.COM) wrote:


: >The markup language crowd learned its lesson long ago: Please, no
: >optical markup. Add explicite tags to your document. Why don't we
: >stay with that?


: But why must writing programs be like writing a document with a
: markup language? IMHO, we already have plenty of problems with
: maintainability as it is.


To diverge slightly; Algol68 took a slightly different approach and
didn't use generic brackets. It used if ... fi, case ... esac, do ... od.
It intially looks ugly but you get used to it in a few days and it is easier
than { ... } and there are fewer mistakes. No what the @#$% does }
supposed to match. No missing brackets. Overloading of syntatic marks
causes mistakes, like the comma, semicolon, less-than-greater-than, of C++.


Ken Walter
[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]
--


Post a followup to this message

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