From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15426 invoked by alias); 1 Jan 2003 12:26:03 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 15412 invoked by uid 71); 1 Jan 2003 12:26:02 -0000 Date: Wed, 01 Jan 2003 12:26:00 -0000 Message-ID: <20030101122602.15411.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Nathanael Nerode Subject: Re: c++/8982: "using foo::operator+" doesn't parse Reply-To: Nathanael Nerode X-SW-Source: 2003-01/txt/msg00000.txt.bz2 List-Id: The following reply was made to PR c++/8982; it has been noted by GNATS. From: Nathanael Nerode 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.