From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21006 invoked by alias); 12 Feb 2004 04:34:19 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 20999 invoked from network); 12 Feb 2004 04:34:18 -0000 Received: from unknown (HELO redhat.com) (66.30.22.40) by sources.redhat.com with SMTP; 12 Feb 2004 04:34:18 -0000 Received: by redhat.com (Postfix, from userid 201) id CAC84400167; Wed, 11 Feb 2004 23:34:17 -0500 (EST) Date: Thu, 12 Feb 2004 04:34:00 -0000 From: Christopher Faylor To: gdb-patches@sources.redhat.com Subject: Re: [patch/rfc] "tui" Message-ID: <20040212043417.GA324@redhat.com> Mail-Followup-To: gdb-patches@sources.redhat.com References: <402923AD.7060104@gnu.org> <20040210184009.GA28778@nevyn.them.org> <20040210125326.6ae7e4ba@saguaro> <20040211131122.GA2333@white> <402A4086.9020702@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <402A4086.9020702@gnu.org> User-Agent: Mutt/1.4.1i X-SW-Source: 2004-02/txt/msg00314.txt.bz2 On Wed, Feb 11, 2004 at 09:47:34AM -0500, Andrew Cagney wrote: >Speaking of which, if that tcl/tk code ever integrated into GDB's code >base (assuming it's first contributed), it to will need a name: tclgdb, >tkgdb, and even gdbtk come to mind (ah, the ultimate irony). If you are going to call it tclgdb or gdbtk then gdb itself should be renamed to cgdb or maybe c-gdb, or gdb-c. And, I suppose, it should also be gdb-c-tui or c-gdb-tui, etc. When the c++ port finally materializes then we can have c++-gdb or gdb-c++. Or, maybe we don't have to mention what the code is written in or for and call it gdbgui or gdbw. Or, hey, gdb could pop up an "insight" window when the DISPLAY environment variable was set! Yeah, that's the ticket. cgf