From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29649 invoked by alias); 9 Nov 2009 19:29:12 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 29639 invoked by uid 22791); 9 Nov 2009 19:29:11 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org From: Tom Tromey To: Sami Wagiaalla Cc: Project Archer Subject: Re: [RFC] Koenig lookup patch 3 References: <49BABABE.9080606@redhat.com> <49F87751.8050405@redhat.com> <4A969900.6040100@redhat.com> <4AD6340F.9070108@redhat.com> <4AD63BA4.4070309@redhat.com> <4AEF2E3C.30601@redhat.com> Reply-To: Tom Tromey Date: Mon, 09 Nov 2009 19:29:00 -0000 In-Reply-To: <4AEF2E3C.30601@redhat.com> (Sami Wagiaalla's message of "Mon, 02 Nov 2009 14:08:44 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2009-q4/txt/msg00044.txt.bz2 >>>>> "Sami" == Sami Wagiaalla writes: Tom> It seems like these additions would introduce a parser ambiguity, Tom> because UNKNOWN_NAME could be parsed as adl_func or as name_not_typename Tom> (and hence variable). Tom> Is bison silent about this? Sami> Good point. Same goes for everything that is common between name and Sami> name_no_typename. Anyways I have changed this to: It still seems like the new productions are ambiguous, because UNKNOWN_NAME alone is an `exp'. If bison doesn't give more warnings after the patch, though, then I wouldn't worry about it. Sami> * c-exp.y: Created token UNKOWN_NAME. Sami> Created grammar rules for UNKOWN_NAME. Typo: should be `UNKNOWN'. Other than that this looks good to me. I was curious to know what happens when the current language is C, not C++. Do we still attempt ADL? Tom