Re: c++/8977: g++ 3.2.2 unable to compile some code with template args

Re: c++/8977: g++ 3.2.2 unable to compile some code with template args

[reichelt]

Synopsis: g++ 3.2.2 unable to compile some code with template args

State-Changed-From-To: open->closed
State-Changed-By: reichelt
State-Changed-When: Wed Dec 18 05:53:52 2002
State-Changed-Why:
    Not a bug.
    
    gcc does not know the identifier ostream_iterator and fails
    with a parse error. If you add
    #include <iterator>
    to your program (as required by the ISO standard), everything works fine.
    
    BTW, Intels compiler seems to import ostream_iterator also with
    #include <vector>
    which is wrong.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8977

Re: c++/8977: g++ 3.2.2 unable to compile some code with template args

[Djalil CHAFAI]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]

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

From: Djalil CHAFAI <chafai@math.ups-tlse.fr>
To: reichelt@igpm.rwth-aachen.de, djalil.chafai@laposte.net,
   gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
   gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/8977: g++ 3.2.2 unable to compile some code with template args
Date: Wed, 18 Dec 2002 16:10:51 +0100 (MET)

 On 18 Dec 2002 reichelt@igpm.rwth-aachen.de wrote:
 > Synopsis: g++ 3.2.2 unable to compile some code with template args
 > State-Changed-From-To: open->closed
 > State-Changed-By: reichelt
 > State-Changed-When: Wed Dec 18 05:53:52 2002
 > State-Changed-Why:
 >     Not a bug.
 >     gcc does not know the identifier ostream_iterator and fails
 >     with a parse error. If you add
 >     #include <iterator>
 >     to your program (as required by the ISO standard), everything works fine.
 >     BTW, Intels compiler seems to import ostream_iterator also with
 >     #include <vector>
 >     which is wrong.
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8977
 
 Thanks for your explanation. If I understand, g++-3.0 and Intel icc
 7.0 are both wrong and g++-3.2 is the closer to the standard. 
 
 Best,
 
 PS: is there a need to delete my bug report?
 
 --
 Djèlil Chafaï - http://www.lsp.ups-tlse.fr/Chafai/