public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Artem Khodush" <artem@duma.gov.ru>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/3462: base class ctor in initializer list problem
Date: Thu, 28 Jun 2001 10:36:00 -0000	[thread overview]
Message-ID: <20010628173601.4029.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR c++/3462; it has been noted by GNATS.

From: "Artem Khodush" <artem@duma.gov.ru>
To: <David.Partridge@primeur.com>
Cc: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>
Subject: Re: c++/3462: base class ctor in initializer list problem
Date: Thu, 28 Jun 2001 21:19:42 +0400

 > template<class o> class asn_occupiedsetof : public asn_setof<o> {
 > public:
 >   asn_occupiedsetof(security_t s = ASN_PUBLIC) : asn_setof(s) {
 >     ASN_OBJTYPE("OSETOF");
 >     set_empty_permitted(false);
 >   };
 >   asn_occupiedsetof(unsigned children, security_t s = ASN_PUBLIC) 
 >   : asn_setof(children, s) {
 >     ASN_OBJTYPE("OSETOF");
 >     set_empty_permitted(false);
 >   };
 > };
 > 
 
 ...
 
 > We're actualy trying to fire the base class ctor of course,
 
 And the name for that class is asn_setof<o>, not just asn_setof.
 
 > not to initialise a field, but it seems g++ has got a bit
 > confused - I think - I'm not a language lawyer on templated
 > classes with inheritance :-(
 > 
 
 I'm not a language lawyer too, but I'm pretty sure that
 in standard c++, only the name of template class itself
 may appear in the class definition not followed by <>.
 The names of any other classes, including bases, must
 always be spelled in full.
 
 
 


             reply	other threads:[~2001-06-28 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28 10:36 Artem Khodush [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-25  6:52 nathan
2001-06-28  8:06 David.Partridge

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=20010628173601.4029.qmail@sourceware.cygnus.com \
    --to=artem@duma.gov.ru \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).