public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/4707: g++ complains about a "typedef", but no typedefs are there
Date: Wed, 04 Dec 2002 06:26:00 -0000	[thread overview]
Message-ID: <20021204142602.27525.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org, Volker Reichelt <reichelt@igpm.rwth-aachen.de>,
   <dlux@dlux.dlux.hu>
Cc:  
Subject: Re: c++/4707: g++ complains about a "typedef", but no typedefs are
 there
Date: Wed, 4 Dec 2002 08:21:49 -0600 (CST)

 The real error of course is the lack of a semicolon after the struct 
 declaration. This brings the typedef into the trouble with the class. If I 
 add the semicolon, I get a much more reasonable message:
 
 tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -c x.cc
 x.cc: In member function `void A<T>::foo()':
 x.cc:3: error: parse error before `;' token
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 
 


             reply	other threads:[~2002-12-04 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04  6:26 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-04  2:26 Volker Reichelt
2001-10-27  4:46 lerdsuwa

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=20021204142602.27525.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --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).