From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32091 invoked by alias); 21 Feb 2003 17:08:03 -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 32078 invoked from network); 21 Feb 2003 17:08:03 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 21 Feb 2003 17:08:03 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id A21D92EF9; Fri, 21 Feb 2003 12:12:41 -0500 (EST) Message-ID: <3E565E09.9020706@redhat.com> Date: Fri, 21 Feb 2003 17:08:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.0.2) Gecko/20030217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jim Blandy , Elena Zannoni Cc: Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: [drow@mvista.com: Re: RFA: LOC_COMPUTED support] References: <20030213211157.GA13537@nevyn.them.org> <20030221152420.GA32260@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00519.txt.bz2 Just a generic heads up on the structure of this code and these, er, batons (from the point of view of the architecture). This is implementing something like (I've not hacked C++ in > 10 years): // some base classes class A; class B; // a derived class (wonder if I got the order right). class B::class B1; // A `uses' B but is parameterized with the specific instance class A->method (class B B); in C. I honestly think that using baton's distract from what is a simple O-O construct and standard O-O terminology. The frame and architecture code both reflect this structure - pass in the object and then use methods supplied as part of the object. Once all this is settled, I think I'll look to re-factor (hmm, buzword) the code so that its structure better refects what is going on. enjoy, Andrew