From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10723 invoked by alias); 28 Sep 2012 07:58:09 -0000 Received: (qmail 10715 invoked by uid 22791); 28 Sep 2012 07:58:06 -0000 X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 28 Sep 2012 07:58:01 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1THVSS-00010l-6s from Yao_Qi@mentor.com ; Fri, 28 Sep 2012 00:58:00 -0700 Received: from SVR-ORW-FEM-05.mgc.mentorg.com ([147.34.97.43]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 28 Sep 2012 00:58:00 -0700 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-05.mgc.mentorg.com (147.34.97.43) with Microsoft SMTP Server id 14.1.289.1; Fri, 28 Sep 2012 00:57:58 -0700 Message-ID: <50655887.2090406@codesourcery.com> Date: Fri, 28 Sep 2012 07:58:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: Eli Zaretskii CC: Subject: Re: [PATCH 1/2] new memory-changed MI notification. References: <1348793347-12556-1-git-send-email-yao@codesourcery.com> <1348793347-12556-2-git-send-email-yao@codesourcery.com> <83bogqha4t.fsf@gnu.org> In-Reply-To: <83bogqha4t.fsf@gnu.org> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-09/txt/msg00669.txt.bz2 On 09/28/2012 03:36 PM, Eli Zaretskii wrote: > If @var{type} can only be "code", then I suggest to say > > ...[,type=code] > > explicitly. > @var{type} can only "code" nowadays, but I am wondering we may have other types, such as "data", in the future. I don't want to give the consumer of this notification an impression that "type=code" is hard-coded into notification. If we don't have to worry about it at all, "[,type=code]" is fine to me. > Btw, why "code"? If this is the name of the section, it should be > ".text", not code. From the consumer of this notification's point of view, 'type' is more useful than 'name', because the consumer may don't know what ".text" section is, or on some ports, text section is not named as ".text", such as section ".text_vle" for VLE. -- Yao