From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: Manush Dodunekov <manush@litecom.se>
Cc: gcc@gcc.gnu.org
Subject: Re: possible bug
Date: Tue, 27 Jul 1999 03:37:00 -0000 [thread overview]
Message-ID: <oraesibcq0.fsf@cupuacu.lsd.dcc.unicamp.br> (raw)
In-Reply-To: <Pine.LNX.4.10.9907271221020.7382-100000@pulse.litecom.net>
On Jul 27, 1999, Manush Dodunekov <manush@litecom.se> wrote:
> 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?
`typename' is required before template-dependent qualified type
names.
> Shouldn't the first case be enough?
It'll probably work without -pedantic, but it is a gcc extension,
don't count on it.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{dcc.unicamp.br,guarana.{org,com}} aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them
WARNING: multiple messages have this Message-ID
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: Manush Dodunekov <manush@litecom.se>
Cc: gcc@gcc.gnu.org
Subject: Re: possible bug
Date: Sat, 31 Jul 1999 23:33:00 -0000 [thread overview]
Message-ID: <oraesibcq0.fsf@cupuacu.lsd.dcc.unicamp.br> (raw)
Message-ID: <19990731233300.i7UYwdh9KduW_NbASjzH4edh_ZAIr3vn_tBwhbtRdOQ@z> (raw)
In-Reply-To: <Pine.LNX.4.10.9907271221020.7382-100000@pulse.litecom.net>
On Jul 27, 1999, Manush Dodunekov <manush@litecom.se> wrote:
> 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?
`typename' is required before template-dependent qualified type
names.
> Shouldn't the first case be enough?
It'll probably work without -pedantic, but it is a gcc extension,
don't count on it.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{dcc.unicamp.br,guarana.{org,com}} aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them
next prev parent reply other threads:[~1999-07-27 3:37 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
1999-07-27 3:37 ` Alexandre Oliva [this message]
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=oraesibcq0.fsf@cupuacu.lsd.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=gcc@gcc.gnu.org \
--cc=manush@litecom.se \
/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).