From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26265 invoked by alias); 3 Jun 2010 20:31:37 -0000 Received: (qmail 26257 invoked by uid 22791); 3 Jun 2010 20:31:37 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 03 Jun 2010 20:31:33 +0000 Received: (qmail 12229 invoked from network); 3 Jun 2010 20:31:31 -0000 Received: from unknown (HELO macbook-2.local) (stan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 3 Jun 2010 20:31:31 -0000 Message-ID: <4C081113.2030201@codesourcery.com> Date: Thu, 03 Jun 2010 20:31:00 -0000 From: Stan Shebs User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: tromey@redhat.com CC: Doug Evans , gdb-patches@sourceware.org Subject: Re: [RFA] add note on command naming to gdbint.texi References: <20100603181353.E965584396@ruffy.mtv.corp.google.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2010-06/txt/msg00109.txt.bz2 Tom Tromey wrote: >>>>>> "Doug" == Doug Evans writes: >>>>>> > > Doug> I'd like to add this to the Coding section of gdbint.texi. > > Doug> +GDB U/I commands are written @samp{foo-bar}, not @samp{foo_bar}. > > I wonder whether we also have a rule about when to use a hyphen versus > when to use a subcommand. > I think it's been semi-random to date (or is that "semi random"? :-) ). It would make sense to suggest using subcommands if there are going to be several related commands for which "foo" is a sensible name for the group. It shouldn't be required though, since for instance the permissions patch I'm working on has commands "set may-write-registers" and "set may-insert-breakpoints", but "set may write-registers" is just going to be mystifying. The suggestion should also mention the possibility of using "bar" as the common subcommand prefix, if the grouping is more logical or easier to remember that way. For instance, I never used to remember whether it was "set remote-debug" or "set debug-remote", but "debug remote" is easy because now it's part of the debug group of set commands. Stan