From: Manush Dodunekov <manush@litecom.se>
To: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: gcc@gcc.gnu.org
Subject: Re: possible bug
Date: Tue, 27 Jul 1999 03:27:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.9907271221020.7382-100000@pulse.litecom.net> (raw)
In-Reply-To: <orwvvnpa4u.fsf@cacau.lsd.dcc.unicamp.br>
On 26 Jul 1999, Alexandre Oliva wrote:
> On Jul 25, 1999, Manush Dodunekov <manush@litecom.se> wrote:
>
> > The code below compiles fine with no flags, but fails to compile with a
> > parse error on the line containing "iterator i;" when compiling with
> > -pedantic.
>
> That's correct. Members of template-dependent base classes must be
> explicitly qualified. Without -pedantic, gcc accepts it as an
> extension.
However, using
vector<T>::iterator i;
doesn't help the compile; It only compiles when using
typename vector<T>::iterator i;
What does the standard say on this? Shouldn't the first case be enough?
regards,
Manush
WARNING: multiple messages have this Message-ID
From: Manush Dodunekov <manush@litecom.se>
To: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: gcc@gcc.gnu.org
Subject: Re: possible bug
Date: Sat, 31 Jul 1999 23:33:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.9907271221020.7382-100000@pulse.litecom.net> (raw)
Message-ID: <19990731233300.AQ5OX0lnyV-hpwMmzHYu5RbiWxzAOzUoeC_wQItXYac@z> (raw)
In-Reply-To: <orwvvnpa4u.fsf@cacau.lsd.dcc.unicamp.br>
On 26 Jul 1999, Alexandre Oliva wrote:
> On Jul 25, 1999, Manush Dodunekov <manush@litecom.se> wrote:
>
> > The code below compiles fine with no flags, but fails to compile with a
> > parse error on the line containing "iterator i;" when compiling with
> > -pedantic.
>
> That's correct. Members of template-dependent base classes must be
> explicitly qualified. Without -pedantic, gcc accepts it as an
> extension.
However, using
vector<T>::iterator i;
doesn't help the compile; It only compiles when using
typename vector<T>::iterator i;
What does the standard say on this? Shouldn't the first case be enough?
regards,
Manush
next prev parent reply other threads:[~1999-07-27 3:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-25 17:52 Manush Dodunekov
1999-07-26 10:57 ` Alexandre Oliva
1999-07-27 3:27 ` Manush Dodunekov [this message]
1999-07-27 3:37 ` Alexandre Oliva
1999-07-31 23:33 ` Alexandre Oliva
1999-07-31 23:33 ` Manush Dodunekov
1999-07-31 23:33 ` Alexandre Oliva
1999-07-31 23:33 ` Manush Dodunekov
-- strict thread matches above, loose matches on Subject: below --
2011-03-26 20:28 Possible Bug Nathan Boley
2011-03-27 7:38 ` Ian Lance Taylor
2011-03-28 11:06 ` Paolo Bonzini
2011-03-28 11:28 ` Richard Guenther
2011-03-28 11:47 ` Paolo Bonzini
2011-03-28 12:14 ` Richard Guenther
2011-03-28 13:37 ` Michael Matz
2011-03-28 13:54 ` Paolo Bonzini
2011-03-28 14:37 ` Richard Guenther
2011-03-29 16:03 ` Nathan Boley
2003-01-31 0:33 possible bug Andrew Morton
2003-01-31 0:36 ` Jan Hubicka
2003-01-31 0:56 ` Andrew Morton
2003-01-31 8:08 ` Alexandre Oliva
2003-01-31 10:48 ` Fergus Henderson
1997-12-12 15:46 Possible Bug Mike Sullivan
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=Pine.LNX.4.10.9907271221020.7382-100000@pulse.litecom.net \
--to=manush@litecom.se \
--cc=gcc@gcc.gnu.org \
--cc=oliva@dcc.unicamp.br \
/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).