From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31740 invoked by alias); 30 Apr 2002 19:01:30 -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 31710 invoked from network); 30 Apr 2002 19:01:26 -0000 Received: from unknown (HELO tetsuo.nj.caldera.com) (63.124.204.226) by sources.redhat.com with SMTP; 30 Apr 2002 19:01:26 -0000 Received: from caldera.com (localhost.localdomain [127.0.0.1]) by tetsuo.nj.caldera.com (8.11.6/8.11.6) with ESMTP id g3UJC3904765; Tue, 30 Apr 2002 15:12:03 -0400 Message-ID: <3CCEEC82.3B6A1298@caldera.com> Date: Tue, 30 Apr 2002 12:01:00 -0000 From: Petr Sorfa Organization: Caldera X-Accept-Language: en MIME-Version: 1.0 To: Michael Elizabeth Chastain CC: msnyder@redhat.com, gdb-patches@sources.redhat.com, shebs@apple.com Subject: Re: [RFC] FORTRAN95 Expression parser References: <200204301810.g3UIAuE13676@duracef.shout.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg01162.txt.bz2 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. 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