public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* c++/8545: failure to parse object declaration
@ 2002-11-19 14:36 tom.widmer
  0 siblings, 0 replies; only message in thread
From: tom.widmer @ 2002-11-19 14:36 UTC (permalink / raw)
  To: gcc-gnats


>Number:         8545
>Category:       c++
>Synopsis:       failure to parse object declaration
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 12 04:46:03 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Tom Widmer
>Release:        3.2
>Organization:
>Environment:
Reading specs from c:/Dev-C++/bin/../lib/gcc-lib/mingw32/3.2/specs
Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host=
mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable
-languages=f77,c++,objc,ada --disable-win32-registry --disable-shared
Thread model: win32
gcc version 3.2 (mingw special 20020817-1)
>Description:
The following code fails to compile:

class test{};
int main() {
    test t((test()));
}

The error is:
main.cpp: In function `int main()':
main.cpp:3: parse error before `)' token

I disagree with this error, and so does Comeau C++ 4.3. The declaration can be parsed as an object declaration (but not a function one), so why isn't it?
>How-To-Repeat:
$ echo "class test{};int main(){test t((test()));}" > main.cpp
$ g++ main.cpp
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-11-12 12:46 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-11-19 14:36 c++/8545: failure to parse object declaration tom.widmer

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