public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Espie <espie@quatramaran.ens.fr>
To: gcc@gcc.gnu.org
Subject: Re: definition of "implicit" inline?
Date: Sat, 02 Aug 2003 17:21:00 -0000	[thread overview]
Message-ID: <200308021034.h72AYq932323@quatramaran.ens.fr> (raw)
In-Reply-To: <20030731110801.1CDCAF2E19@nile.gnat.com>

I think you're jumping on Gaby for the wrong reasons.
C++ has an `inline' concept.

Both syntactic forms, the one with the inline keyword, and the one
that declares the method within the class, are equivalent.

Now, what the compiler does with the corresponding code is something
else. As long as it behaves `as if' the function body had been substituted
in place, it is fine.

But making or implying a semantic distinction between both syntactic
forms is a bad idea, which is why Gaby is strongly against the name
`implicit inline' for a semantic distinction.

C++ is a large language. Even with an existing standard, it still has
an history. This history muddles things up. Heck, old versions of g++
muddle things up even more.  And new stuff in C99 won't help.

Trying to keep things as simple as they can be, as Gaby is doing, is
a good thing.

Or maybe you are shooting down C++ for its lack of precise semantics,
especially compared to Ada ? Well, you're definitely right there, but
that doesn't make Gaby wrong :)

  parent reply	other threads:[~2003-08-02 10:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 13:12 Robert Dewar
2003-07-31 13:37 ` Gabriel Dos Reis
2003-08-02 17:21 ` Marc Espie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-31 13:53 Robert Dewar
2003-07-31 13:58 ` Gabriel Dos Reis
2003-07-31 14:00   ` Gabriel Dos Reis
2003-07-31 11:59 Robert Dewar
2003-07-31 12:41 ` Gabriel Dos Reis
2003-07-31 11:02 Robert Dewar
2003-07-31 11:04 ` Gabriel Dos Reis
2003-07-31 10:02 Martin Reinecke
2003-07-31 10:08 ` Gabriel Dos Reis
2003-07-31 10:50 ` Andreas Schwab

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=200308021034.h72AYq932323@quatramaran.ens.fr \
    --to=espie@quatramaran.ens.fr \
    --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).