From: Eli Zaretskii <eliz@gnu.org>
To: "Jim Blandy" <jimb@red-bean.com>
Cc: jimb@codesourcery.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: prologue value modules
Date: Tue, 28 Mar 2006 21:17:00 -0000 [thread overview]
Message-ID: <uodzqbe9f.fsf@gnu.org> (raw)
In-Reply-To: <8f2776cb0603281029y35c11fb9v2ad31f4a0445d6b3@mail.gmail.com> (jimb@red-bean.com)
> Date: Tue, 28 Mar 2006 10:29:37 -0800
> From: "Jim Blandy" <jimb@red-bean.com>
> Cc: "Jim Blandy" <jimb@codesourcery.com>, gdb-patches@sources.redhat.com
>
> > Would it be a good idea to have the listing of the API in the manual,
> > with short explanations? I'm not saying it is necessarily required,
> > but please give it a thought.
>
> I'd rather have the API described in the header file. I don't think
> we, as a project, can afford to maintain two copies of that sort of
> documentation, and I think the header files are best place for
> detailed, function-by-function information.
But that's contrary to the rest of gdbint.texinfo, which does document
the more important parts of the respective APIs.
> How does this look?
Looks good, thanks.
next prev parent reply other threads:[~2006-03-28 18:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 5:20 Jim Blandy
2006-03-23 5:24 ` Daniel Jacobowitz
2006-03-23 5:32 ` Randolph Chung
2006-03-23 5:39 ` Jim Blandy
2006-03-23 14:06 ` Jim Blandy
2006-03-24 1:03 ` Jim Blandy
2006-03-24 2:40 ` Jim Blandy
2006-03-28 7:51 ` Jim Blandy
2006-03-24 14:48 ` Eli Zaretskii
2006-03-24 22:43 ` Jim Blandy
2006-03-28 2:24 ` Jim Blandy
2006-03-28 18:58 ` Eli Zaretskii
2006-03-28 19:15 ` Jim Blandy
2006-03-28 21:17 ` Eli Zaretskii [this message]
2006-03-28 21:59 ` Jim Blandy
2006-04-07 19:19 ` Ulrich Weigand
2006-04-08 23:40 ` Jim Blandy
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=uodzqbe9f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@codesourcery.com \
--cc=jimb@red-bean.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