From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8410 invoked by alias); 30 Apr 2002 19:13:37 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 8399 invoked from network); 30 Apr 2002 19:13:35 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 30 Apr 2002 19:13:35 -0000 Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id MAA06341; Tue, 30 Apr 2002 12:13:29 -0700 (PDT) Message-ID: <3CCEE9EB.AADF0940@redhat.com> Date: Tue, 30 Apr 2002 12:13:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Accept-Language: en MIME-Version: 1.0 To: Petr Sorfa CC: Michael Elizabeth Chastain , gdb-patches@sources.redhat.com, shebs@apple.com Subject: Re: [RFC] FORTRAN95 Expression parser References: <200204301810.g3UIAuE13676@duracef.shout.net> <3CCEEC82.3B6A1298@caldera.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg01166.txt.bz2 Petr Sorfa wrote: > > Hi All, > > Thanks for all the input and comments. > > The side-by-side integration was my original intention, so that once > everybody realizes how great the new F95 parser is then a quick switch > can be done. Note that I'm thinking of automatically enabling it for > F90/F95 binaries (as long as they are appropriately marked by the DWARF > language attribute.) To do this I'll add a new language to gdb - > fortran95 > > Since the parser full functionality depends on many features touching > DWARF support, column major support, variable evaluation, location > expression, new scoping, etc.. which will require separate code reviews > and comments. I'll initially release the parser as a "crimped" version. > Basically it will do the parsing, but will raise an error if any of the > unsupported features are used. I'll be adding the other features > separately and enable the various functionality of the parser as it goes > on. > > I'm hoping to roll out everything over the next couple of weeks. The > test suite update will be put in early as well. Sounds like a good plan. > Even with this roll-out plan I personally think that the initial > "crimped" version will be more robust than the existing FORTRAN parser. > > Petr > > > Coincidentally, I was looking at a FORTRAN pr this morning. > > > > I think the existing FORTRAN expression parser is lame and I would > > not miss it. > > > > I favor the side-by-side strategy. Keep the files as f95-x files. > > Let the gdb people play with it side by side. If the new interface > > dominates the old interface, we can remove the old f-x files. > > If we think there will be a constituency for the old interface, > > then we can release both. > > > > The problem with merging is that it makes the code much less readable > > and makes it harder to discard the old code. > > > > My two cents, > > > > Michael C