public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: carlo@alinoe.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/9217: Possible Ambiguity leads to confusing error, or - compiler rejects legal-code: fails to solve ambiguity.
Date: Tue, 07 Jan 2003 13:16:00 -0000	[thread overview]
Message-ID: <20030107130624.17755.qmail@sources.redhat.com> (raw)


>Number:         9217
>Category:       c++
>Synopsis:       Possible Ambiguity leads to confusing error, or - compiler rejects legal-code: fails to solve ambiguity.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 07 05:16:04 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Carlo Wood
>Release:        3.2.1
>Organization:
>Environment:

>Description:
I don't know if this is a compiler bug - but we thought
that the real guru's should have a look at it, just in case.

g++ -c troep.cc
troep.cc: In function `void f()':
troep.cc:10: cannot declare static function inside another function
>How-To-Repeat:
Compile the following code with g++ -c troep.cc

struct A { A(char const*); };
struct B { B(A const&); };
struct C { C(B const&); };

void f()
{
  char const* const str = "t";
  static C c1(  B("t")  );      // Works.
  static C c2( (B(str)) );      // Works.
  static C c3(  B(str)  );      // Fails.
}



>Fix:

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


             reply	other threads:[~2003-01-07 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 13:16 carlo [this message]
2003-01-07 13:31 nathan

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=20030107130624.17755.qmail@sources.redhat.com \
    --to=carlo@alinoe.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).