Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/wip] Save/restore cooked registers
Date: Mon, 26 Aug 2002 13:52:00 -0000	[thread overview]
Message-ID: <1020826203733.ZM32100@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@ges.redhat.com> "Re: [patch/wip] Save/restore cooked registers" (Aug 26,  2:21pm)

On Aug 26,  2:21pm, Andrew Cagney wrote:

> > I've looked over Andrew's WIP patch.  I haven't checked all the details,
> > but the ideas seem sound and the interfaces look okay.  I'd like to see
> > the iterators better commented though.
> 
> The doco will go in:
> gdbint.texinfo:Registers:Saving and Restoring Registers.

As I understand it, functions should be commented in the source
files too.  (Cf. http://www.gnu.org/prep/standards_24.html#SEC24)

When I'm working on gdb, I find it more convenient to go to the
location of the function declaration / definition and read the
associated comment.  I do look at the texinfo document too, but only
as a last resort.  (I trust it less, plus I find that the markup gets
in the way of easy comprehension.)

> Hence ``wip'' :-)

Okay.

Kevin


  reply	other threads:[~2002-08-26 20:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 12:23 Andrew Cagney
2002-08-26  9:05 ` Kevin Buettner
2002-08-26  9:31   ` Andrew Cagney
2002-08-26 10:26   ` Elena Zannoni
2002-08-26 11:21     ` Kevin Buettner
2002-08-26 11:25       ` Andrew Cagney
2002-08-26 13:52         ` Kevin Buettner [this message]
2002-08-26 11:29       ` Elena Zannoni
2002-08-26 12:04         ` Kevin Buettner
2002-08-28  7:42         ` Richard Earnshaw
2002-08-28  9:58           ` Andrew Cagney
2002-08-29  8:36             ` Elena Zannoni

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=1020826203733.ZM32100@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.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