From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8350 invoked by alias); 9 Oct 2003 19:39:39 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 8341 invoked from network); 9 Oct 2003 19:39:38 -0000 Received: from unknown (HELO zenia.home) (12.223.225.216) by sources.redhat.com with SMTP; 9 Oct 2003 19:39:38 -0000 Received: by zenia.home (Postfix, from userid 5433) id E2F8920766; Thu, 9 Oct 2003 14:38:05 -0500 (EST) To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: target_op(..) -> target_op(target, ...) obvious References: <3F855EFF.9080300@redhat.com> From: Jim Blandy Date: Thu, 09 Oct 2003 19:39:00 -0000 In-Reply-To: <3F855EFF.9080300@redhat.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-10/txt/msg00160.txt.bz2 Andrew Cagney writes: > As part of the on-going OO of GDB, the "target vector" is one of the > next things up for treatment. I'd like to be sure that everyones ok > with the mechanical transformatioin: > > target_OP (...) -> taget_OP (target, ...) > > being considered "fairly obvious" (post patch, give it a few days, > commit patch). Pushing the target around is going to involve touching > files across maintenance boundraries. So, in this patch, the calls would all pass a pointer to the global variable 'current_target', right? Or would it also include changes to functions' interfaces to pass the target around explicitly?