This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: streambuf.h:403: parse error before `ios'
- From: Boyan Biandov <bbiandov at SEIU790 dot org>
- To: "'llewelly at xmission dot com'" <llewelly at xmission dot com>
- Cc: "'gcc-help at gcc dot gnu dot org'" <gcc-help at gcc dot gnu dot org>
- Date: Sun, 2 May 2004 21:29:49 -0700
- Subject: RE: streambuf.h:403: parse error before `ios'
Excellent, this will explain the behavior. What is the default assumption
meaning what file extension would each compiler assume and also how would
one force the compiler to ignore the extension as a language descriptor and
interpret it as specified by the user (may be a command line parameter here)
thanks
-----Original Message-----
From: llewelly@xmission.com [mailto:llewelly@xmission.com]
Sent: Sunday, May 02, 2004 8:32 PM
To: Boyan Biandov
Cc: 'gcc-help@gcc.gnu.org'
Subject: Re: streambuf.h:403: parse error before `ios'
Boyan Biandov <bbiandov@SEIU790.org> writes:
> Thanks,
>
> I have few machines, one of which is 3.4.0 under RH9 and I get the
> same exact errors. Now a bit of interesting fact I just discovered:
>
> If I use c++ -O3 -o test test.c -Wall -I/usr/include/g++-3/ it
> compiles just fine
>
> But gcc -O3 -o test test.c -Wall -I/usr/include/g++-3/ generates parse
> errors in fstream and iostream
[snip]
This is a different problem. 'gcc' will assume a '.c' file is C, not
C++. However, 'g++' will assume a '.c' file is C++, not C.