🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.std.unix
Article #538

Re: Standards Update, U.S. TAG to ISO/IEC/JTC1/SC22 WG15

#538
From: Richard A. O'Keefe
Date: Mon, 01 Oct 1990 05:50
42 lines
2712 bytes
Submitted-by: ok@goanna.cs.rmit.OZ.AU (Richard A. O'Keefe)

In article <559@usenix.ORG> in comp.std.unix,
jsh@usenix.org (Jeffrey S. Haemer) wrote:

> We cannot delay language independence for 1003.1 any longer.  It's now
> really holding up international progress on important POSIX efforts.
> But what format or technique should we use?  ISO rules seem to require
                                               *************************
> an ISO-standard method, which could restrict us to VDM (Vienna
****************************************************************
> Definition Method), but no one thinks VDM will work.  Paul Rabin and
********************
> Steve Walli have been working on a method, but the TAG worries that a
> non-standard method will create problems like those we've suffered
> through with document formats (see last TAG report).  In order to
> avoid rejection later we will circulate the new method in SC22 and
> WG15 for review and comment.  To make this circulation useful, Donn
> Terry is listing specific questions for SC22 and WG15 to answer.
> [Editor: I believe that ISO rules only restrict us to VDM if we
> produce a formal definition, i.e., something from which one could do
> correctness proofs.  Of course, rules and politics are not always the
> same thing and using VDM might help grease the skids.  Still, we
> should stop and ask if not using VDM would hold us up any more than
> using VDM.]

My main interest here is in the ISO Prolog standard.  I am confused by
this extract from comp.std.unix, because the ISO Prolog standard
contains a formal specification of Prolog.  Personally, I would find it
easier to read if it _were_ in VDM.  Instead it's in a variant of
first-order logic (exact semantics unknown) with a new syntax.  This
definition was developed with the explicit intention of permitting
correctness proofs.  Does this mean that ISO _will_ accept "make up your
own formal specification language", or does it mean that the Prolog
specification in the ISO Prolog draft is forbidden by ISO rules?

Can someone who really knows clear this up?

-- 
Fixed in the next release.

Volume-Number: Volume 21, Number 156
Technical Details
Message-ID: <564@usenix.ORG>
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!usenix!jsq
References: <559@usenix.ORG>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!usenix!jsq
From: ok@goanna.cs.rmit.OZ.AU (Richard A. O'Keefe)
Newsgroups: comp.std.unix,comp.lang.prolog
Subject: Re: Standards Update, U.S. TAG to ISO/IEC/JTC1/SC22 WG15
Message-ID: <564@usenix.ORG>
Date: 1 Oct 90 05:50:43 GMT
References: <559@usenix.ORG>
Sender: jsq@usenix.ORG
Followup-To: comp.lang.prolog
Organization: Comp Sci, RMIT, Melbourne, Australia
Lines: 42
Approved: jsq@usenix.org (Moderator, John Quarterman)
X-Submissions: std-unix@uunet.uu.net