public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: valentin_iancu@yahoo.com To: gcc-gnats@gcc.gnu.org Subject: c++/10309: No specific error message when the base class is not defined Date: Fri, 04 Apr 2003 13:06:00 -0000 [thread overview] Message-ID: <20030404125719.28447.qmail@sources.redhat.com> (raw) >Number: 10309 >Category: c++ >Synopsis: No specific error message when the base class is not defined >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Fri Apr 04 13:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: valentin_iancu@yahoo.com >Release: gcc version 3.2 20020927, 20020903 >Organization: >Environment: OS: Win2k / cygwin i686 ALSO linux RH 8 3.2 20020903 (Red Hat Linux 8.0 3.2-7) /netrel/src/gcc-3.2-3/configure --enable-languages=c,c++,f77,java --enable-libgcj --enable-threads=posix --with-system-zlib --enable-nls --without-included-gettext --enable-interpreter --disable-sjlj-exceptions --disable-version-specific-runtime-libs --enable-shared --build=i686-pc-linux --host=i686-pc-cygwin --target=i686-pc-cygwin --enable-haifa --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --includedir=/nonexistent/include --libexecdir=/usr/sbin >Description: gcc gives an erronated "parse" error, when it's actually a semantic error when declaring a class that has a base class undefined. The famous code: //Start the file class A : public B { }; //End the file Class B is undefined here, and the error message says: t.cpp:4: parse error before `{' token I expect here an error that says : <<base class undefined>>! >How-To-Repeat: :-D copy & paste may be? >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-04-04 13:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-04 13:06 valentin_iancu [this message] 2003-04-04 17:33 bangerth
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=20030404125719.28447.qmail@sources.redhat.com \ --to=valentin_iancu@yahoo.com \ --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: linkBe 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).