From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-22136-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 10977 invoked by alias); 11 Jul 2005 07:06:55 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 10912 invoked by uid 22791); 11 Jul 2005 07:06:49 -0000
Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 11 Jul 2005 07:06:49 +0000
Received: from farnswood.snap.net.nz (p238-tnt2.snap.net.nz [202.124.108.238])
	by viper.snap.net.nz (Postfix) with ESMTP id 02A265D0890;
	Mon, 11 Jul 2005 19:06:46 +1200 (NZST)
Received: by farnswood.snap.net.nz (Postfix, from userid 501)
	id A728962A99; Mon, 11 Jul 2005 07:50:13 +0100 (BST)
From: Nick Roberts <nickrob@snap.net.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17106.5796.850869.491390@farnswood.snap.net.nz>
Date: Mon, 11 Jul 2005 07:06:00 -0000
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Formatting of function pointer value
In-Reply-To: <dat0jr$kuh$3@sea.gmane.org>
References: <dalbrd$tn0$1@sea.gmane.org>
	<20050708135810.GB17089@nevyn.them.org>
	<dat0jr$kuh$3@sea.gmane.org>
X-SW-Source: 2005-07/txt/msg00099.txt.bz2

 > > It is a feature, not a bug.  Why is your frontend using the
 > > command-line interface?  
 > 
 > Well, the debugger part in KDevelop was not written by me, so I don't know
 > why command-line interface, and not MI is used.
 > 
 > > DON'T do that!  Use MI nowadays, please please 
 > > please.
 > 
 > I'm sorry, but section 24 of gdb manual does not say why MI is better. Can
 > you give the reasons?

CLI output is intended for the user.  It can change with a new release, and on
the state of execution in ways which are not easy to anticipate without
reading the source code.  Provided that it still makes sense, that is not a
problem to the user but it can be to a frontend, if it is trying to parse the
output in a very precise manner.  MI has a more formal syntax and so is not as
variable.  Once it is fully developed, its output should be stable and if it
does change, some backward compatibility will probably be maintained.

Nick