From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] cleanup stale exec.{h|c} xfer_memory comments.
Date: Sat, 13 Jun 2009 03:47:00 -0000 [thread overview]
Message-ID: <E1MFKCv-000806-VP@fencepost.gnu.org> (raw)
In-Reply-To: <200906121943.08246.pedro@codesourcery.com> (message from Pedro Alves on Fri, 12 Jun 2009 19:43:07 +0100)
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Fri, 12 Jun 2009 19:43:07 +0100
>
> The comment describing section_table_xfer_memory_partial is actually
> still describing the old xfer_memory. This removes that stale
> description, and adjusts the description in the header a bit better
> to current reality.
Is the convention to describe functions in headers? That's reasonable
for data structures, but we have a lot of functions documented right
before their source, not in the headers. I find the documentation in
the .c files easier to use, because you don't need to consult another
file. This is C, not C++, so the interface and the implementation are
not separated.
next prev parent reply other threads:[~2009-06-13 3:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 18:41 Pedro Alves
2009-06-13 3:47 ` Eli Zaretskii [this message]
2009-06-13 11:12 ` Joel Brobecker
2009-06-15 18:31 ` Tom Tromey
2009-06-16 0:20 ` Joel Brobecker
2009-06-23 19:59 ` Stan Shebs
2009-06-23 20:54 ` Tom Tromey
2009-06-13 11:48 ` Pedro Alves
2009-06-13 12:24 ` Eli Zaretskii
2009-06-13 13:26 ` Pedro Alves
2009-06-13 13:31 ` Eli Zaretskii
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=E1MFKCv-000806-VP@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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