From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22227 invoked by alias); 4 Jun 2012 20:49:32 -0000 Received: (qmail 22218 invoked by uid 22791); 4 Jun 2012 20:49:32 -0000 X-SWARE-Spam-Status: No, hits=-6.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 04 Jun 2012 20:49:16 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q54KnFV1025516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 4 Jun 2012 16:49:15 -0400 Received: from psique ([10.3.113.17]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q54KnC5v010003; Mon, 4 Jun 2012 16:49:14 -0400 From: Sergio Durigan Junior To: Mark Kettenis Cc: tromey@redhat.com, gdb-patches@sourceware.org Subject: Re: [PATCH 03/10] C language References: <1338665528-5932-1-git-send-email-sergiodj@redhat.com> <1338665528-5932-4-git-send-email-sergiodj@redhat.com> <87lik2n7ik.fsf@fleche.redhat.com> <201206042042.q54Kg4mU002330@glazunov.sibelius.xs4all.nl> X-URL: http://www.redhat.com Date: Mon, 04 Jun 2012 20:49:00 -0000 In-Reply-To: <201206042042.q54Kg4mU002330@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Mon, 4 Jun 2012 22:42:04 +0200 (CEST)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-06/txt/msg00101.txt.bz2 On Monday, June 04 2012, Mark Kettenis wrote: > I hesitated to bring it up, but when I was looking into using the yacc > -p option to get rid of the #defines, the underscored names posed a > problem. > > So if you go through the trouble of renaming things, it might make > sense to use a consistent prefix ($LANG_) and give the wrappers > different names. Do you mean what Tom meant (i.e., using `$LANG_parse_internal' instead of `_$LANG_parse'), or a bigger change? -- Sergio