|Formatting of Language LRMs firstname.lastname@example.org (Seima Rao) (2014-06-17)|
|Re: Formatting of Language LRMs email@example.com (Ivan Godard) (2014-06-20)|
|Re: Formatting of Language LRMs Pidgeot18@verizon.net.invalid (=?UTF-8?B?Sm9zaHVhIENyYW5tZXIg8J+Qpw==?=) (2014-06-22)|
|RE: Formatting of Language LRMs firstname.lastname@example.org (Costello, Roger L.) (2014-07-03)|
|Re: Formatting of Language LRMs email@example.com (Ivan Godard) (2014-07-03)|
|Re: executable semantics, was Formatting of Language LRMs firstname.lastname@example.org (2014-07-04)|
|From:||email@example.com (William Clodius)|
|Date:||Fri, 4 Jul 2014 15:53:01 -0600|
|References:||14-06-010 14-06-016 14-06-021 14-07-004 14-07-009|
|Posted-Date:||06 Jul 2014 19:06:30 EDT|
Ivan Godard <firstname.lastname@example.org> wrote:
> How would it differ from a document containing,
> > say, Java?
> If the document were a compiler written in Java (i.e. a recognizer and
> checker) then formally there is no difference. Practically, an immense
> difference. VWG is an ASL for specifying languages. All of Algol68 in
> VWG was about four pages of appendix; a compiler for Algol68 written in
> Java would be much more than that, even after you strip out optimization
> and code generation.
> Also, the specification in VWG lends itself to use of metatools: make a
> change to the grammar and verify that the revision is complete,
> consistent and not redundant. Not something easy to do when the language
> is expressed by a Java recognizer.
FWIW if I remember correctly a varient of that belief led the Modula II
standard to attempt to descibe the langauage using the Vienna Definition
Method. They hoped to verify the formal description automatically, but
they could not afford the commercial tools and the implementation of one
of the participants was not ready in time when they decided they had to
get it out the door.
Return to the
Search the comp.compilers archives again.