public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: dewar@gnat.com (Robert Dewar)
To: aph@redhat.com, gcc@gcc.gnu.org
Subject: Re: c++ "with" keyword
Date: Sat, 04 Jan 2003 17:06:00 -0000	[thread overview]
Message-ID: <20030104162506.E11CFF2D4F@nile.gnat.com> (raw)

> See Algol 68 for what happens if you do it the other way...

I am willing to bet that this comment is made with *ZERO* knowledge
about Algol-68. In fact the Algol-68 standard was remarkably complete
and successful, and in environments where full Algol-69 compilers
became available (notably on the ICL-9000 and CDC-6000 series machines
it was widely used). The issue of why it was not more successful is
a commercial/marketing one, which had very little if anything to do
with the way the standard was produced.

I am certainly not opposed to experimentation with new features
using existing compilers (GNAT has been used this way in the Adaq
community, for example we implemented "with type" pretty early on
and partly as a result of this experience, we have learned that it
was not the best approach). But discussion and suggestions of new
features are best carried out in forums primarily populated by
users and language designers, rather than compiler implementors.

Another danger of course is that if a half baked feature is
implemented, then it gets stuck and never removed (we will in
fact remove the "WITH TYPE" feature in GNAT when a better
substitute comes along, even though it will discombobulate
people). It is too easy to argue for keeping junk stuff around
for compatibility reasons (witness recent thread here in which
some argued that junk illegal semicolons should be accepted in
C++ due to the existence of incorrect code :-)


             reply	other threads:[~2003-01-04 16:25 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04 17:06 Robert Dewar [this message]
2003-01-04 17:22 ` Daniel Berlin
2003-01-05 11:33 ` Andrew Haley
2003-01-05 11:36   ` Toon Moene
2003-01-05 14:17   ` [GCC] " Trevor Jenkins
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06 13:07 Robert Dewar
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-06 12:18 ` Andrew Haley
2003-01-05 12:56 Robert Dewar
2003-01-05 18:22 ` Joseph S. Myers
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 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=20030104162506.E11CFF2D4F@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).