From: Brian Rogoff <bpr@shell5.ba.best.com>
Subject: Re: Standadised OO Language
Date: 1998/02/13
Date: 1998-02-13T00:00:00+00:00 [thread overview]
Message-ID: <Pine.BSF.3.96.980213105023.20666A-100000@shell5.ba.best.com> (raw)
In-Reply-To: 34E48B7B.2A5D@lmco.com
On Fri, 13 Feb 1998, Howard W. LUDWIG wrote:
> Perhaps some specific dates and details would help:
>
> CLOS (Common Lisp Object System)
> 1994-12-08 ANSI X3.226:1994
> ---------- has not become an ISO standard
To be precise (this is the Ada newsgroup after all :-), one should say
"Common Lisp", not CLOS, as CLOS is just an object system sitting on top
of the objectless ANSI CL subset.
> ISLISP (which I know very little about and haven't kept up with any
> details,
> other than it is supposed to be neither a subset nor a superset
> of CLOS!!!)
> 1997-??-?? ISO 13816:1997
> ---------- has not become an ANSI standard
Never finished, supposedly based on EuLisp, a nice clean Lisp which never
went anywhere. Its a sort of reaction to the fact that Common Lisp was
originally an all-American, or rather all-USA grass roots effort to
synthesize a Lisp out of the extant US Lisps. EuLisp was a brand new
design somewhere between Scheme and Common Lisp in the design space.
Some of the story is in the HOPL-II proceedings.
> [Thus, Lisp has the dubious distinction of being one of the few
> languages for
> which both an ANSI standard and an ISO standard exist but they never
> have matched
> nor does there seem to be any attempt to harmonize them.]
Last time I looked ISO Lisp wasn't finished, so I'm not sure if this is
true. I'll look at the ISO web page when I have a web connection.
>
> Ada 95 has been a published ISO standard for 3 years now (well, after
> two
> more days, actually :), and this version is a revision of a previous ISO
> standard. Mature compilers from several vendors for several
> [understatement]
> platforms are available in a _validated_ form. The validation process
> for
> Ada 95 compilers has been growing in rigor, following a transition time
> of
> relative laxness from Ada 83 to Ada 95. GNAT, which runs on a wide
> variety
> of platforms, implements the full (including all optional annexes)
> language
> and passes _all_ relevant validation tests.
> There is no mechanism in place to assure compliance of compilers to the
> standard (like Ada validation).
This is a big plus for Ada, much more important IMO than whether an ANSI
or ISO standard exists.
> Since it is expected
> that a revision to the C standard will be approved in 1999 or 2000 and
> C++ has been intricately coupled in structure with C [which is a whole
> other issue and a can of worms in itself], the C++ folks are already
> talking about mechanisms for C++ compiler vendors to modify their C++
> compilers to handle the revisions to the C standard without adjusting
> the C++ standard!?#!
Excellent point, which I hadn't really thought of. Of course, it may also
entail some slight modification to Annex B of Ada 95.
As Robert Dewar pointed out, none of this is likely to sway anyone who has
already decided that they "hate" language X, where X is Ada, C++, Lisp, or
whatever. I know I prefer Ada over C++, but C++ has some nice ideas too.
-- Brian
next prev parent reply other threads:[~1998-02-13 0:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-12 0:00 Standadised OO Language Matthew Daniel
1998-02-12 0:00 ` Standardized " Markus Kuhn
1998-02-13 0:00 ` Stephen Leake
1998-02-13 0:00 ` Jon S Anthony
1998-02-17 0:00 ` Terry Devine
1998-02-12 0:00 ` Standadised " Mark Bennison
1998-02-12 0:00 ` Kenneth W. Sodemann
1998-02-12 0:00 ` David Weller
1998-02-12 0:00 ` Brian Rogoff
1998-02-12 0:00 ` Robert Dewar
1998-02-12 0:00 ` Jon S Anthony
1998-02-13 0:00 ` Kenneth W. Sodemann
1998-02-13 0:00 ` Howard W. LUDWIG
1998-02-13 0:00 ` Brian Rogoff [this message]
1998-02-13 0:00 ` William Clodius
1998-02-15 0:00 ` Dennis Reimer
-- strict thread matches above, loose matches on Subject: below --
1998-02-14 0:00 Marc Wachowitz
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox