From: dewar@gnat.com (Robert Dewar)
To: aph@redhat.com, dewar@gnat.com
Cc: gcc@gcc.gnu.org
Subject: Re: c++ "with" keyword
Date: Mon, 06 Jan 2003 13:07:00 -0000 [thread overview]
Message-ID: <20030106121755.1C290F28E4@nile.gnat.com> (raw)
> a. Algol 68 was not implemented at the time it was specified
True also of COBOL-90, C++, Ada
But in any case why is this bad? It may simply mean that you have done a
good job of specification and have managed to do that earlier. There is no
inherent merit in delaying specification. Indeed in general in software,
the concept of specify before implementation is not usually considered
a bad thing :-)
> b. Full Algol 68 was hard to implement given the resources available
Well yes, so what? That's not an argument for delaying its specification
until it was implemented.
> c. The difficuly of implementing the full language hurt its sucess
But it would not have been implemented at all if it had not been specified
and published by WG2.1, so again this is not an argument for delaying
specification.
Part of the trouble with modern complex languages is that they are not
one-person-hobbyist-working-in-their-spare-time-to-make-prototype projects.
So in practice large teams are needed for implementation. That makes it
even more essential to have clear specifications.
Your argument that somehow Algol-68 (or any other language) is harmed
by accurate early specification in detail is definitely not convincing.
next reply other threads:[~2003-01-06 12:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 13:07 Robert Dewar [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 18:41 Robert Dewar
2003-01-05 13:03 Robert Dewar
2003-01-05 13:39 ` Toon Moene
2003-01-05 12:56 Robert Dewar
2003-01-05 18:22 ` Joseph S. Myers
2003-01-05 12:56 Robert Dewar
2003-01-06 12:18 ` Andrew Haley
2003-01-05 12:44 Robert Dewar
2003-01-05 3:16 Robert Dewar
2003-01-05 0:38 Robert Dewar
2003-01-05 0:29 Robert Dewar
2003-01-05 0:37 ` Kevin Handy
2003-01-04 23:27 Robert Dewar
2003-01-04 23:36 ` Lynn Winebarger
2003-01-05 2:55 ` Gianni Mariani
2003-01-04 22:13 Robert Dewar
2003-01-04 20:59 Robert Dewar
2003-01-04 22:36 ` Gianni Mariani
2003-01-04 20:09 Robert Dewar
2003-01-04 19:36 Robert Dewar
2003-01-04 19:59 ` Tolga Dalman
2003-01-04 19:13 Robert Dewar
2003-01-04 20:58 ` Gianni Mariani
2003-01-04 18:11 Robert Dewar
2003-01-04 18:47 ` Gianni Mariani
2003-01-04 17:52 Robert Dewar
2003-01-04 17:59 ` Gianni Mariani
2003-01-04 17:06 Robert Dewar
2003-01-04 17:22 ` Daniel Berlin
2003-01-05 11:33 ` Andrew Haley
2003-01-05 11:36 ` Toon Moene
2003-01-04 14:29 Robert Dewar
2003-01-04 15:00 ` Momchil Velikov
2003-01-04 15:24 ` Andrew Haley
2003-01-04 16:25 ` Neil Booth
2003-01-04 17:35 ` Gianni Mariani
2003-01-04 17:59 ` Tolga Dalman
2003-01-04 18:36 ` Gianni Mariani
2003-01-04 18:54 ` Tolga Dalman
2003-01-04 23:32 ` Kevin Handy
2002-12-29 8:32 Norman Jonas
2002-12-29 12:46 ` Russ Allbery
2002-12-29 6:49 Erik Schnetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030106121755.1C290F28E4@nile.gnat.com \
--to=dewar@gnat.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).