From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24574 invoked by alias); 13 May 2006 08:09:49 -0000 Received: (qmail 24566 invoked by uid 22791); 13 May 2006 08:09:49 -0000 X-Spam-Check-By: sourceware.org Received: from romy.inter.net.il (HELO romy.inter.net.il) (192.114.186.66) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 13 May 2006 08:09:48 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-243-9.inter.net.il [83.130.243.9]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id EED77581 (AUTH halo1); Sat, 13 May 2006 11:09:44 +0300 (IDT) Date: Sat, 13 May 2006 08:45:00 -0000 Message-Id: From: Eli Zaretskii To: pgilliam@us.ibm.com CC: gdb-patches@sourceware.org In-reply-to: <1147460632.3672.81.camel@dufur.beaverton.ibm.com> (message from PAUL GILLIAM on Fri, 12 May 2006 12:03:52 -0700) Subject: Re: CLI and GDB/MI documentation patch Reply-to: Eli Zaretskii References: <20060512011730.GA26655@brasko.net> <20060512124940.GB3860@nevyn.them.org> <20060512135802.GA6472@nevyn.them.org> <20060512183723.GA14434@nevyn.them.org> <1147460632.3672.81.camel@dufur.beaverton.ibm.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00277.txt.bz2 > From: PAUL GILLIAM > Cc: gdb-patches@sourceware.org > Date: Fri, 12 May 2006 12:03:52 -0700 > > On Fri, 2006-05-12 at 21:55 +0300, Eli Zaretskii wrote: > > > If you feel we should tell how to create a front end and/or a stub > > that supports several versions of GDB/MI or remote protocol, that's > > fine by me, but let's have sections whose focus is to provide tips to > > such programmers, not to tell the history of MI or the protocol's > > evolution. That's quite a different attitude than what Bob wrote. > > Why not have a section in the internals manual: something like > "How to (and not to) write frontends for GDB"? That was the essence of my suggestion. The manual in which that section will appear is less important. FWIW, I feel that it should be in the user manual, since gdbint describes the GDB internals, which this issue isn't part of. Also, since both the remote protocol and MI are described in the user manual, the reader interested in writing a stub or a front end will naturally look for this stuff in the same document.