From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18453 invoked by alias); 15 Jan 2008 21:38:29 -0000 Received: (qmail 18445 invoked by uid 22791); 15 Jan 2008 21:38:28 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 15 Jan 2008 21:38:02 +0000 Received: from kahikatea.snap.net.nz (226.62.255.123.dynamic.snap.net.nz [123.255.62.226]) by viper.snap.net.nz (Postfix) with ESMTP id E41F43DA52A; Wed, 16 Jan 2008 10:37:59 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 340D48FC6D; Wed, 16 Jan 2008 10:37:51 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18317.10158.443444.852081@kahikatea.snap.net.nz> Date: Tue, 15 Jan 2008 21:38:00 -0000 To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Subject: Re: [BUG:MI] -break-list doesn't list multiple breakpoints In-Reply-To: References: <18310.38708.144719.374963@kahikatea.snap.net.nz> <18311.64973.546980.107837@kahikatea.snap.net.nz> X-Mailer: VM 7.19 under Emacs 23.0.50.30 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: 2008-01/txt/msg00369.txt.bz2 > > Refusing requests mentioning CLI and not providing functionality in MI > > seems to leave the frontend developer between a rock and a hard place. > > As a meta-comment, I'd like to point out that I'm a frontend developer, > and I'm in no better position than you in anyway. I don't take comfort in your discomfort! > Now, what do you want -- making sure that all new functionality is available > via MI, or that it's available via CLI? Of course "both CLI and MI" is > a possible answer, but it increases the amount of work and the time till > completion. I would like developers to take care in preserving the format of CLI commands whenever possible. It's easy for global maintainers to make an executive decision not to support the use of CLI in frontends because they may not realise how incomplete MI is. -- Nick http://www.inet.net.nz/~nickrob