From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22732 invoked by alias); 11 Sep 2003 03:33:09 -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 22725 invoked from network); 11 Sep 2003 03:33:09 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 11 Sep 2003 03:33:09 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 63CBDD2DAF; Wed, 10 Sep 2003 20:33:09 -0700 (PDT) Date: Thu, 11 Sep 2003 15:40:00 -0000 From: Joel Brobecker To: Elena Zannoni , gdb@sources.redhat.com Subject: Re: vast numbers of unimplemented MI commands. Message-ID: <20030911033309.GB945@gnat.com> References: <20030911020429.GF17937@white> <16223.58420.108851.41512@localhost.redhat.com> <20030911031111.GG17937@white> <20030911032502.GA945@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030911032502.GA945@gnat.com> User-Agent: Mutt/1.4i X-SW-Source: 2003-09/txt/msg00154.txt.bz2 > Somebody like you for instance (who understands the needs of GDB > frontends because he's developping one) who also invests time into > making GDB/MI better. See for instance one of the commands that > our GVD (our graphical front-end) needed: What we did was simply propose > a new command, discussed it, and then implemented it. And I forgot to say: it may seem that working both on your frontend and GDB is increase your amount of work. But on the crontrary, I think this approach is going to save you some time in the long run. Based on the GVD experience, the less CLI output you have to parse, the better off you'll be. -- Joel