From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21358 invoked by alias); 24 Oct 2003 20:48:27 -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 21343 invoked from network); 24 Oct 2003 20:48:26 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 24 Oct 2003 20:48:26 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 2B6892B89 for ; Fri, 24 Oct 2003 16:48:27 -0400 (EDT) Message-ID: <3F99901B.6030005@redhat.com> Date: Fri, 24 Oct 2003 20:48:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb-patches@sources.redhat.com Subject: [rfc] New files "memory.[hc]" Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00753.txt.bz2 Hello, At present the old (non target parameterized) memory functions all live in gdbcore.h, and corefile.c (I guess "core" is "core" in the traditional sense :-). What do people think of putting the new (with target parameter) methods, that wrap target_{read,write} in a new file "memory.[hc]"? I think they are going to end up cluttering up "target.[hc]". Andrew