Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C)

Dave Lloyd <dave@occl-cam.demon.co.uk>
1 Mar 1996 13:59:28 -0500

          From comp.compilers

Related articles
[10 earlier articles]
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) k2consult@aol.com (1996-02-26)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) henry@zoo.toronto.edu (Henry Spencer) (1996-02-27)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) anton@complang.tuwien.ac.at (1996-02-27)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) blume@zayin.cs.princeton.edu (1996-02-27)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) przemek@rrdjazz.nist.gov (1996-03-01)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) dave@occl-cam.demon.co.uk (Dave Lloyd) (1996-03-01)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) dave@occl-cam.demon.co.uk (Dave Lloyd) (1996-03-01)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) henry@zoo.toronto.edu (Henry Spencer) (1996-03-01)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) WStreett@shell.monmouth.com (1996-03-03)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) jens.hansson@mailbox.swipnet.se (1996-03-06)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) jens.hansson@mailbox.swipnet.se (1996-03-08)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) rfg@monkeys.com (1996-03-10)
Re: Languages: The Bigger the Uglier (was: Re: Aliasing in ISO C) jan@neuroinformatik.ruhr-uni-bochum.de (1996-03-11)
[2 later articles]
| List of all articles for this month |

From: Dave Lloyd <dave@occl-cam.demon.co.uk>
Newsgroups: comp.compilers
Date: 1 Mar 1996 13:59:28 -0500
Organization: Compilers Central
References: 96-02-248 96-02-304
Keywords: standards, design

> Unfortunately, such contracts work much better if they are written in
> a language that the implementors and the users can understand without
> calling in a specialist to interpret for them. This is why the ANSI C
> committee deliberately decided against formal specifications. The
> fact that much of the audience for the contract cannot read formal
> specs is regrettable, but it is a fact and it will not change any time
> soon.


The Algol 68 committee took the other view, with one important twist:
the language report was written in a very formal style, including as
thorough a description of the method of description, but the committee
also sponsored a book to teach the language to programmers quickly and
easily (the Informal Introduction, a masterpiece IMHO). Most people
use the Informal as their reference but it gives them the grounding of
understanding the Report. It helps that Algol 68 is a very uniform
language with very few odd constraints.


> In the real world, contracts are not written in Esperanto, despite the
> theoretical advantages of doing so.


ROTFL. You strangle yourself with your own argument! Have you read
any of the legalese in big commercial contracts recently - only the
lawyers retained by each side actually understand it, the signatories
just take the word of their lawyers that it means what they want and
will stand up in court. Law (English or American) is a perfect
example of specifications understood only by the insiders.


----------------------------------------------------------------------
Dave Lloyd Email: Dave@occl-cam.demon.co.uk
Oxford and Cambridge Compilers Ltd Phone: (44) 1223 572074
55 Brampton Rd, Cambridge CB1 3HJ, UK
--


Post a followup to this message

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