From: "Eli Zaretskii" <eliz@gnu.org>
To: "Dave Korn" <dk@artimi.com>
Cc: cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: Discussion: Formalizing the deprecation process in GDB
Date: Fri, 08 Oct 2004 13:38:00 -0000 [thread overview]
Message-ID: <01c4ad38$Blat.v2.2.2$abd73c80@zahav.net.il> (raw)
In-Reply-To: <NUTMEGznXgffHr1qmd600000322@NUTMEG.CAM.ARTIMI.COM> (dk@artimi.com)
> From: "Dave Korn" <dk@artimi.com>
> Cc: <cagney@gnu.org>,
> <gdb@sources.redhat.com>
> Date: Fri, 8 Oct 2004 13:40:31 +0100
>
> Eli, I was particularly thinking of you when I wrote
>
> " It's just occurred to me that this could be read as a specific complaint
> or accusation against gdb's documentation, rather than a comment on the
> generally sorry state of documentation as a whole in the software industry.
> No such inference was implied nor intended; sorry if anyone thought I was
> criticising gdb with that statement! "
I, for one, don't see your criticism as a Bad Thing; on the contrary.
> However, since we mention it, sections 3.3-3.6, 4.3-4.4, 9.7-9.9,
> 10.3-10.6, 11.2-11.5, 12.3-12.4 and 12.7 of gdbint are missing.
Just so it is easier for me to find those places, could you please
tell the names of these sections, instead of just numbers?
> Also, 9.5 and 9.6 are both prefixed with disclaimers; 9.5 says "This
> section is pretty much obsolete. The functionality described here has
> largely been replaced by pseudo-registers and the mechanisms described [...
> in 9.6 ...] " and refers the reader to 9.6, which says "The way GDB
> manipulates registers is undergoing significant change. Many of the macros
> and functions refered to in this section are likely to be subject to further
> revision.". The combined effect of these two sections is to leave the
> reader (well, this one, at any rate) with no idea how you're supposed to
> manipulate registers (or indeed, what a pseudo-register even is, since the
> term is not used nor defined anywhere else in the documentation). And I
> didn't find that browsing the comments in regcache.h makes up for that.
I agree that such ``documentation'' is very unhelpful. Would someone
please volunteer to write something more useful?
next prev parent reply other threads:[~2004-10-08 13:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 17:55 Joel Brobecker
2004-09-27 20:35 ` Eli Zaretskii
2004-10-06 6:14 ` Andrew Cagney
2004-10-06 13:39 ` Eli Zaretskii
2004-10-07 4:48 ` Joel Brobecker
2004-10-07 14:27 ` Dave Korn
2004-10-07 15:12 ` Joel Brobecker
2004-10-07 16:16 ` Andrew Cagney
2004-10-07 18:50 ` Dave Korn
2004-10-07 16:14 ` Andrew Cagney
2004-10-07 18:08 ` Dave Korn
2004-10-07 19:18 ` Joel Brobecker
2004-10-07 19:28 ` Dave Korn
2004-10-08 7:08 ` Joel Brobecker
2004-10-08 12:13 ` Eli Zaretskii
2004-10-08 12:05 ` Eli Zaretskii
2004-10-08 8:54 ` Fabian Cenedese
2004-10-08 11:45 ` Eli Zaretskii
2004-10-08 19:22 ` Andrew Cagney
2004-10-10 21:31 ` Eli Zaretskii
2004-10-08 10:45 ` Eli Zaretskii
2004-10-08 13:31 ` Dave Korn
2004-10-08 13:38 ` Eli Zaretskii [this message]
2004-10-08 13:43 ` Dave Korn
2004-10-08 13:44 ` Dave Korn
2004-10-08 19:16 ` Eli Zaretskii
2004-10-08 19:45 ` Eli Zaretskii
2004-10-08 22:10 ` Andrew Cagney
2004-10-08 10:38 ` Eli Zaretskii
2004-10-11 15:11 ` Andrew Cagney
2004-10-12 7:34 ` Eli Zaretskii
2004-10-12 13:42 ` Mark Kettenis
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='01c4ad38$Blat.v2.2.2$abd73c80@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=dk@artimi.com \
--cc=gdb@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