public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/16598] New: apparent typo in bits/fstream.tcc
@ 2004-07-17  1:51 victor dot secarin at shaw dot ca
  2004-07-17  1:54 ` [Bug libstdc++/16598] " pinskia at gcc dot gnu dot org
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: victor dot secarin at shaw dot ca @ 2004-07-17  1:51 UTC (permalink / raw)
  To: gcc-bugs

My application failed to build, complaining that "an unqualified id was
expected" at line 277 in /usr/local/include/c++/3.4.1/bits/fstream.tcc
The whole file is inside an "namespace std" block. 
At lines 277 and 518 are two calls to std::min. 
Replacing "std::min" with just "min" solved the problem.

-- 
           Summary: apparent typo in bits/fstream.tcc
           Product: gcc
           Version: 3.4.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: victor dot secarin at shaw dot ca
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16598


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2004-07-20 19:28 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20040717015120.16598.vsecarin@paradigmgeo.com>
2004-07-19 13:15 ` [Bug libstdc++/16598] apparent typo in bits/fstream.tcc bangerth at dealii dot org
2004-07-20 19:28 ` vsecarin at paradigmgeo dot com
2004-07-17  1:51 [Bug c++/16598] New: " victor dot secarin at shaw dot ca
2004-07-17  1:54 ` [Bug libstdc++/16598] " pinskia at gcc dot gnu dot org
2004-07-17 17:36 ` pinskia at gcc dot gnu dot org
2004-07-17 17:52 ` pinskia at gcc dot gnu dot org

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).