public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@cs.tu-berlin.de>
To: gcc-gnats@gcc.gnu.org
Cc: 87000-quiet@bugs.debian.org
Subject: c++/2957: -pedantic: parse error
Date: Sat, 26 May 2001 11:16:00 -0000	[thread overview]
Message-ID: <E153iTG-0001mf-00@smile.cs.tu-berlin.de> (raw)

>Number:         2957
>Category:       c++
>Synopsis:       -pedantic: parse error
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 26 11:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Debian BTS #87000
>Release:        3.0 20010526 (Debian prerelease) (Debian testing/unstable)
>Organization:
Debian
>Environment:
System: Linux smile 2.2.17 #1 Sun Oct 8 19:26:41 MEST 2000 i686 unknown
Architecture: i686

	
host: i386-pc-linux-gnu
build: i386-pc-linux-gnu
target: i386-pc-linux-gnu
configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,objc --prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-x --without-included-gettext --disable-checking --enable-threads=posix --enable-java-gc=boehm --with-cpp-install-dir=bin --enable-objc-gc i386-linux
>Description:
	
example below compiled witch -pedantic makes: 
 
$ g++-3.0 -pedantic foo.cc 
foo.cc: In function `int foo()': 
foo.cc:8: parse error before `;' token 
 
w/o -pedantic it is ok.  
 
 
#include <vector> 
 
using namespace std; 
 
template<class T> 
int foo() 
{ 
        vector<T>::iterator i; /* this line: parse error before ';' */ 
} 
 
 
int main(){return 0;} 
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-05-26 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-26 11:16 Matthias Klose [this message]
2001-05-27  2:16 Gabriel Dos Reis
2001-05-28  3:46 Artem Khodush

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=E153iTG-0001mf-00@smile.cs.tu-berlin.de \
    --to=doko@cs.tu-berlin.de \
    --cc=87000-quiet@bugs.debian.org \
    --cc=gcc-gnats@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).