From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7520 invoked by alias); 8 Dec 2002 20:52:16 -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 7513 invoked from network); 8 Dec 2002 20:52:14 -0000 Received: from unknown (HELO neon-gw.transmeta.com) (63.209.4.196) by sources.redhat.com with SMTP; 8 Dec 2002 20:52:14 -0000 Received: (from root@localhost) by neon-gw.transmeta.com (8.9.3/8.9.3) id MAA17153; Sun, 8 Dec 2002 12:52:02 -0800 Received: from mailhost.transmeta.com(10.1.1.15) by neon-gw.transmeta.com via smap (V2.1) id xma017117; Sun, 8 Dec 02 12:51:32 -0800 Received: from casey.transmeta.com (casey.transmeta.com [10.10.25.22]) by deepthought.transmeta.com (8.11.6/8.11.6) with ESMTP id gB8KpaR24464; Sun, 8 Dec 2002 12:51:36 -0800 (PST) Received: (from dje@localhost) by casey.transmeta.com (8.9.3/8.7.3) id MAA24584; Sun, 8 Dec 2002 12:51:35 -0800 From: Doug Evans MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15859.45271.946698.844275@casey.transmeta.com> Date: Sun, 08 Dec 2002 12:52:00 -0000 To: Daniel Jacobowitz Cc: fnasser@redhat.com, gdb@sources.redhat.com Subject: Re: Processing of convenience variables for scripts ... In-Reply-To: <20021208203043.GA17271@nevyn.them.org> References: <20021120163549.GA14036@nevyn.them.org> <20021120183613.GA24089@nevyn.them.org> <200212081936.LAA24307@casey.transmeta.com> <20021208203043.GA17271@nevyn.them.org> X-SW-Source: 2002-12/txt/msg00167.txt.bz2 Daniel Jacobowitz writes: > > add-symbol-file takes a file name as the first argument and > > you can't store strings (of any kind) in convenience variables. > > > > I haven't checked FSF sources in the last few months, > > maybe things have improved. If so great. If not, how would this work? > > This is true. One problem at a time - numbers first. I have some > ideas, but I won't have a chance to work on this until next weekend. Well, ... If one is going to do a redesign of things one should at least think about all the known issues before doing any coding. [I'm sure there's no news there.] Do we at least know how we're going to handle strings, and what compatibleness with existing usage we're going to break? btw, while doing a redesign of the cli is laudable, the more I work with gdb's command structure the more I like its simplicity. I wouldn't mind regularizing the syntax of arguments such that one can know one can always use buildargv (or some such). And providing an sscanf-like routine that *_command fns can call would also be useful. Beyond that I dunno ....