Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>,
		Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [mi] [ada] varobjs for registers 2
Date: Sat, 30 Dec 2006 20:30:00 -0000	[thread overview]
Message-ID: <20061230203016.GB25539@nevyn.them.org> (raw)
In-Reply-To: <20061221072102.GF3640@adacore.com> <200612202137.29038.vladimir@codesourcery.com>

On Wed, Dec 20, 2006 at 09:37:28PM +0300, Vladimir Prus wrote:
> 
> This is a second revision of the patch to add MI command that
> creates varobjs for registers. The command is renamed to -var-list
> and used like:
> 
> 	-var-list --registers
> 
> There are now docs and tests. The created variable objects no longer
> have 'public' pseudo-fields, no matter what the language of the program is.
> 
> Along the way, I've promoted a private function in ada-lang.c to language.c,
> so I'd appreciate if Ada maintainers take a quick look.
> 
> OK?

Before I look at this, is it the latest version?  You and Nick had an
active discussion about this while I was on vacation.

On Thu, Dec 21, 2006 at 11:21:02AM +0400, Joel Brobecker wrote:
> I believe the comment describing the function should be placed besides
> the function implementation, in language.c. This is the habit we have
> at least in the GNU projects I've been involved in. In Ada, we much
> prefer to place the documentation besides the declaration, as you did,
> but C allows you to put as many declarations of the same entity as you
> want, and wherever you want. So this conventions allows us to know
> exactly where the documentation is...

GDB is inconsistent about this, so I don't think it makes much
difference.  I've been putting the comments in headers for global
functions and referring to the header from the implementation,
but that's not great either.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-12-30 20:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 18:38 Vladimir Prus
2006-12-20 19:44 ` Eli Zaretskii
2007-01-05  9:01   ` Vladimir Prus
2007-01-05  9:29     ` Eli Zaretskii
2006-12-21  7:20 ` Joel Brobecker
2006-12-30 20:30   ` Daniel Jacobowitz [this message]
2007-01-05  9:06     ` Vladimir Prus
2007-01-05 10:24       ` Nick Roberts
2007-01-05 10:47         ` Vladimir Prus

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=20061230203016.GB25539@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.com \
    /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