public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Bill Somerville <bill@classdesign.com> To: gcc-gnats@gcc.gnu.org Subject: c++/3406: Parse error on valid expression Date: Mon, 25 Jun 2001 07:36:00 -0000 [thread overview] Message-ID: <200106251424.PAA16144@wallace.classdesign.com> (raw) >Number: 3406 >Category: c++ >Synopsis: ( int() > int() ) gives parse error >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Mon Jun 25 07:36:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Bill Somerville >Release: @gcc_version_full@ >Organization: Class Design Ltd. >Environment: System: Linux wallace.classdesign.com 2.2.9-19mdk #2 Sun Nov 14 18:37:33 GMT 1999 i586 unknown Architecture: i586 host: @host@ build: @build@ target: @target@ configured with: @gcc_config_arguments@ >Description: int main() { ( int() > int() ); return 0; } gives: $ c++ t.cpp t.cpp: In function `int main()': t.cpp:3: parse error before `>' token >How-To-Repeat: See code sample above. Also fails with user defined type default constructor calls. This was detected in a test harness that exercises comparison operators on default constructed objects - perhaps a similar test should be included in the compiler testsuite. >Fix: Not a work around, but if the parenthesis around the offending expression are removed, the expression compiles as expected. In my case not feasable as the expression is mixed with i/o stream inserters. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-06-25 7:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200106251424.PAA16144@wallace.classdesign.com \ --to=bill@classdesign.com \ --cc=gcc-gnats@gcc.gnu.org \ /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: linkBe 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).