public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tkarkanis@aw.sgi.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/8914: parentheses not accepted around constructor call in return statement
Date: Thu, 12 Dec 2002 07:56:00 -0000	[thread overview]
Message-ID: <20021212154833.2799.qmail@sources.redhat.com> (raw)


>Number:         8914
>Category:       c++
>Synopsis:       parentheses not accepted around constructor call in return statement
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 12 07:56:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     tkarkanis@aw.sgi.com
>Release:        3.2
>Organization:
>Environment:
Red Hat Linux
>Description:
If a return statement has parentheses around the expression, and the expression returns a temporary object created by calling the constructor without arguments, g++ emits a parse error.  See attached file.  This problem seems to exist in many versions of gcc.  A workaround is to remove the parentheses enclosing the return expression.
>How-To-Repeat:
g++ -c return.cpp
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="return.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="return.cpp"

Y2xhc3MgRm9vCnsKcHVibGljOgogICAgRm9vKCk7CiAgICBGb28oIGludCApOwp9OwoKRm9vIGYo
KQp7CiAgICAvLyByZXR1cm4gRm9vKCk7ICAgICAgIC8vIHdvcmtzCiAgICAvLyByZXR1cm4oIEZv
bygwKSApOyAgIC8vIHdvcmtzCiAgICByZXR1cm4oIEZvbygpICk7ICAgICAgIC8vIGZhaWxzCn0K


             reply	other threads:[~2002-12-12 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12  7:56 tkarkanis [this message]
2002-12-12  8:18 reichelt

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=20021212154833.2799.qmail@sources.redhat.com \
    --to=tkarkanis@aw.sgi.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: link
Be 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).