From: Joel Brobecker <brobecker@gnat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Enhance GDB to break inside DSO init code
Date: Sat, 24 Jul 2004 15:01:00 -0000 [thread overview]
Message-ID: <20040724150104.GP20596@gnat.com> (raw)
In-Reply-To: <7494-Sat24Jul2004105517+0300-eliz@gnu.org>
> Why, oh why do people go to such great lengths to explain this in a
> mail message and/or in the comments to the code, but not as a patch to
> gdbint.texinfo? Why not invest a small additional effort (Texinfo
> markup) to improve our documentation together with fixing a bug?
To me, explainations about the code belong in the code. When reading
some code I don't know about, I appreciate explainations located right
besides the code I'm trying to understand. I usually don't remember to
look into gdbint or any other document, and besides, it's incovenient
to have to search it, to see if there would be any additional info
there.
If I had to make a suggestion, I would embed all the information from
gdbint inside the code, and make gdbint a document generated from the
code.
--
Joel
next prev parent reply other threads:[~2004-07-24 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 20:24 Joel Brobecker
2004-07-24 7:56 ` Eli Zaretskii
2004-07-24 15:01 ` Joel Brobecker [this message]
2004-07-24 17:16 ` Eli Zaretskii
2004-08-06 18:31 ` Joel Brobecker
2004-08-19 7:55 ` Joel Brobecker
2004-08-24 23:45 ` Kevin Buettner
2004-08-27 13:39 ` Joel Brobecker
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=20040724150104.GP20596@gnat.com \
--to=brobecker@gnat.com \
--cc=eliz@gnu.org \
--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