Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFC/RFA] add struct parse_context to all command functions
Date: Tue, 21 Oct 2008 00:47:00 -0000	[thread overview]
Message-ID: <20081021004630.GA6571@caradoc.them.org> (raw)
In-Reply-To: <1224529335.28191.14.camel@localhost.localdomain>

On Mon, Oct 20, 2008 at 05:02:14PM -0200, Thiago Jung Bauermann wrote:
> El lun, 20-10-2008 a las 09:16 -0700, Joel Brobecker escribió:
> > Har har har, I should be able to be active again soon :-)
> 
> Hooray. :-)
> 
> > So we have 3 alternatives:
> > 
> >   1. All command functions receive the parse_context structure.
> >      Do the transition all at once.

Personally, I prefer this one, unless the person doing the work
(that's you!) doesn't agree.

> THe problem with (3) is that you make the code slightly more complex by
> adding an additional add_*_cmd that the GDB hacker will have to learn
> about.

I also worry that there will end up being a combinatorial explosion of
these things.

> The advantage is that you can avoid writing functions with argument
> they'll never use. I mention this because the ProjectIdeas wiki page
> mentions that it's desirable to have GDB compile with -Wunused.
> 
> IMHO I prefer to use (3) and have the option of using the -Wunused later
> (not that I'm stepping up to the task! :-) ).

Let's not use this as a design decision.  IMO it is not too ugly to
mark unused arguments with e.g. ATTRIBUTE_UNUSED; that's what GCC
does.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-10-21  0:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 14:05 Joel Brobecker
2008-10-09 16:13 ` Tom Tromey
2008-10-09 22:20   ` Joel Brobecker
2008-10-20 16:16 ` Joel Brobecker
2008-10-20 19:03   ` Thiago Jung Bauermann
2008-10-21  0:47     ` Daniel Jacobowitz [this message]
2008-10-21 18:06       ` Ulrich Weigand
2008-10-21 18:18         ` Daniel Jacobowitz
2008-10-22  1:40           ` Joel Brobecker
2008-10-22 20:15             ` Tom Tromey
2008-10-22 20:36               ` Joel Brobecker
2008-10-21  1:22   ` Tom Tromey
2008-10-21  7:07     ` Joel Brobecker
2008-10-21 18:12     ` Ulrich Weigand
2008-10-21 18:58       ` Tom Tromey
2008-10-21 19:33       ` Tom Tromey
2008-10-22 18:03         ` Ulrich Weigand
2008-10-22 18:54           ` Tom Tromey
2008-10-22 22:24             ` Ulrich Weigand
2008-10-23  1:02               ` Tom Tromey
2008-10-23 19:50                 ` Ulrich Weigand
2008-10-23 21:29                   ` Tom Tromey
2008-10-24 13:01                     ` Ulrich Weigand
2008-10-25 16:05                       ` Tom Tromey
2008-10-27 17:07                       ` Tom Tromey
2008-10-28 16:27                         ` Ulrich Weigand
2008-10-28 18:17                           ` Tom Tromey
2008-10-28 20:00                             ` Ulrich Weigand
2008-10-25 16:25                     ` Joel Brobecker
2008-10-25 16:46                       ` Tom Tromey
2008-10-26 15:19                         ` Joel Brobecker
2008-10-21 18:05 ` Ulrich Weigand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081021004630.GA6571@caradoc.them.org \
    --to=drow@false.org \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox