Re: c++/8982: "using foo::operator+" doesn't parse

Re: c++/8982: "using foo::operator+" doesn't parse

[Nathanael Nerode]

The following reply was made to PR c++/8982; it has been noted by GNATS.

From: Nathanael Nerode <neroden@twcny.rr.com>
To: dean@foster.net, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
   nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/8982: "using foo::operator+" doesn't parse
Date: Wed, 1 Jan 2003 07:21:25 -0500

 This appears to work with mainline now that the new parser has been committed.
 
 Does this nead a testcase (and if so where should I put it)?  Once that 
 question is resolved I believe we can close this bug.

Re: c++/8982: "using foo::operator+" doesn't parse

[neroden]

Synopsis: "using foo::operator+" doesn't parse

State-Changed-From-To: analyzed->closed
State-Changed-By: neroden
State-Changed-When: Wed Jan  1 04:37:49 2003
State-Changed-Why:
    Added testcase.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8982

Re: c++/8982: "using foo::operator+" doesn't parse

[Neil Booth]

The following reply was made to PR c++/8982; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.co.uk>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: dean@foster.net, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/8982: "using foo::operator+" doesn't parse
Date: Wed, 1 Jan 2003 12:27:05 +0000

 Nathanael Nerode wrote:-
 
 > This appears to work with mainline now that the new parser has been committed.
 > 
 > Does this nead a testcase (and if so where should I put it)?  Once that 
 > question is resolved I believe we can close this bug.
 
 I think we should put all existing PRs resolved by the new parser in the
 testsuite.
 
 g++.dg/parse
 
 is a possible location.
 
 Neil.

Re: c++/8982: "using foo::operator+" doesn't parse

[reichelt]

Synopsis: "using foo::operator+" doesn't parse

State-Changed-From-To: open->analyzed
State-Changed-By: reichelt
State-Changed-When: Wed Dec 18 07:17:08 2002
State-Changed-Why:
    Confirmed.
    
    Gaby's comment on this (which accidentally ended up as PR 8983):
    > This is a known bug -- there already duplicate reports
    > for this and proposed patch.  And, we'll have the new parser (soon).

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8982

c++/8982: "using foo::operator+" doesn't parse

[dean]

>Number:         8982
>Category:       c++
>Synopsis:       "using foo::operator+" doesn't parse
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 17 08:46:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     dean@foster.net
>Release:        gcc 3.2
>Organization:
>Environment:
linux
>Description:
if you want to inject an operator from a namespace into a file, you need to include the entire namespace.  I don't think this is correct.  See below for an example.  The line with is incorrectly handled is marked:


namespace foo{
  template<class X>
  int bar(X x);
  template<class X>
  int operator- (X x);
}

int main()
{
  using foo::bar;    // works correctly
  using foo::operator-;  // ** complains as syntax error
  using namespace foo;  // will inject operator-
}


>How-To-Repeat:

namespace foo{
 
  template<class X>
  int operator- (X x);
}

int main()
{
 
  using foo::operator-;  // ** complains as syntax error
 
}

>Fix:

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