From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10304 invoked by alias); 25 Aug 2009 09:40:45 -0000 Received: (qmail 10295 invoked by uid 22791); 25 Aug 2009 09:40:44 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_50 X-Spam-Check-By: sourceware.org Received: from mailhost.u-strasbg.fr (HELO mailhost.u-strasbg.fr) (130.79.200.151) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 25 Aug 2009 09:40:38 +0000 Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.14.2/jtpda-5.5pre1) with ESMTP id n7P9eJqO021528 ; Tue, 25 Aug 2009 11:40:19 +0200 (CEST) (envelope-from muller@ics.u-strasbg.fr) Received: from mailserver.u-strasbg.fr (ms1.u-strasbg.fr [IPv6:2001:660:2402:d::10]) by baal.u-strasbg.fr (8.14.0/jtpda-5.5pre1) with ESMTP id n7P9eJ2a074667 ; Tue, 25 Aug 2009 11:40:19 +0200 (CEST) (envelope-from muller@ics.u-strasbg.fr) Received: from d620muller (www-ics.u-strasbg.fr [130.79.210.225]) (user=mullerp mech=LOGIN) by mailserver.u-strasbg.fr (8.14.3/jtpda-5.5pre1) with ESMTP id n7P9eI0K048406 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) ; Tue, 25 Aug 2009 11:40:18 +0200 (CEST) (envelope-from muller@ics.u-strasbg.fr) From: "Pierre Muller" To: "'Keith Seitz'" , Cc: References: <4A9313C2.3050907@redhat.com> <4A9367B2.4040900@redhat.com> In-Reply-To: <4A9367B2.4040900@redhat.com> Subject: RE: [RFA] Token cleanup in c-exp.y Date: Tue, 25 Aug 2009 13:45:00 -0000 Message-ID: <000601ca2568$0eedea60$2cc9bf20$@u-strasbg.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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: 2009-08/txt/msg00411.txt.bz2 Just for information: doesn't this mean that the parser that previously accepted '-> *' with spaces between the arrow and the star, will now reject such patterns? Is this also what a C compile would do? The behavior of GDB did change indeed: Old behavior: (top-gdb) p current_objfile->*gdb_stderr non-pointer-to-member value used in pointer-to-member construct (top-gdb) p current_objfile-> *gdb_stderr non-pointer-to-member value used in pointer-to-member construct New behavior: (top-gdb) p current_objfile->*gdb_stderr non-pointer-to-member value used in pointer-to-member construct (top-gdb) p current_objfile-> *gdb_stderr A syntax error in expression, near `*gdb_stderr'. The problem is that I have no idea what it stands for... and I never saw '->*' nor '.*' in any C sources. Please forgive the question if it is silly, and remember that my knowledge of C is limited to what I learned to be able to contribute to the GDB project... Pierre Muller Pascal language support maintainer for GDB