From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13431 invoked by alias); 30 Nov 2009 20:25:12 -0000 Received: (qmail 13408 invoked by uid 22791); 30 Nov 2009 20:25:11 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 30 Nov 2009 20:25:06 +0000 Received: from mailhost3.vmware.com (mailhost3.vmware.com [10.16.27.45]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id C7DB32901D; Mon, 30 Nov 2009 12:25:02 -0800 (PST) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by mailhost3.vmware.com (Postfix) with ESMTP id BB475CD90D; Mon, 30 Nov 2009 12:25:02 -0800 (PST) Message-ID: <4B1428F0.7090608@vmware.com> Date: Mon, 30 Nov 2009 20:46:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20090624) MIME-Version: 1.0 To: Joel Brobecker CC: Hui Zhu , "gdb@sourceware.org" Subject: Re: [RFC] Let "gcore" command accept a suffix argument References: <4B11DA3C.3000203@vmware.com> <20091130162246.GE4034@adacore.com> <4B141157.3070709@vmware.com> <20091130185341.GI4034@adacore.com> <4B141469.5030402@vmware.com> <20091130190619.GJ4034@adacore.com> In-Reply-To: <20091130190619.GJ4034@adacore.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-11/txt/msg00228.txt.bz2 Joel Brobecker wrote: >> Would it be able to include the incr? "eval gcore foo.$a++"? > > I do not think so, not as suggested by Tom, I believe. The suggestion > is to expand convenience variables, not evaluate full-fledged > expressions. The issue with full-fledged expressions is that you have > to recognize them and find where they start and end. But I think that > this would not be a serious limitation in practice, since the above > can be rewritten as: > > eval gcore foo.$a > set $a = $a + 1 Well, that would suit me OK, so long as somebody else implements it.