Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Klee Dienes <klee@apple.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add stabs entries for coalesced symbols.
Date: Mon, 09 Dec 2002 10:22:00 -0000	[thread overview]
Message-ID: <FD5DA5CC-0B40-11D7-9779-00039396EEB8@apple.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1021209075735.2295F-100000@is>

Yes; thanks for the explanation.

Just to be clear on why I was asking, my concern wasn't that it was the 
only instance of "coalesced symbols" in the document, it was that it 
was the only instance of @cindex in the document, and I was worried 
that an index with only one entry could look awkward.  But I suspect 
after reading your response that your response would be "well, that 
just means we probably need more @cindex entries to be added".

On Monday, December 9, 2002, at 01:06 AM, Eli Zaretskii wrote:
>
>> I ask only because it's the only one in the
>> document.
>
> I'm afraid I don't understand the nature of your hesitance.
>
> An index entry is a powerful means for finding information in the 
> manual
> quickly and efficiently.  It is quick because just typing "i coalesc 
> TAB"
> and then hitting [Enter] will take you to the section you wrote in both
> Emacs and the stand-alone Info reader.  It is efficient because index
> entries are created by humans who are supposed to consider issues that
> users are likely to think about when looking for specific information,
> and therefore the phrases included in the index are already oriented
> towards someone who searches for info.
>
> In other words, indexing helps you use the manual as a reference.  
> Thus,
> whether the term "coalesced symbol" appears once or more than once in a
> manual is not important for having an index entry for it.  On the
> contrary, since there is a definitive place where the manual explains
> what a coalesced symbol is and how GDB handles it, having an index 
> entry
> for that one place is very important.
>
> Does that resolve your concerns?


  reply	other threads:[~2002-12-09  6:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C774777A-FB47-11D6-84AF-00039396EEB8@apple.com>
2002-11-18 16:37 ` Klee Dienes
2002-11-18 22:22   ` Ian Lance Taylor
2002-11-24  2:25     ` Klee Dienes
2002-11-24  6:21       ` Eli Zaretskii
2002-12-08 17:00         ` Klee Dienes
2002-12-08 22:39           ` Eli Zaretskii
2002-12-09 10:22             ` Klee Dienes [this message]
2002-12-09 12:37               ` Eli Zaretskii
2002-11-24  9:46       ` Ian Lance Taylor
2002-11-24 14:22       ` Jim Blandy
2002-12-06  8:59       ` Nick Clifton
2002-11-18 22:59 Eli Zaretskii
     [not found] <1038196445.11584.ezmlm@sources.redhat.com>
2002-11-24 20:21 ` Jim Ingham

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=FD5DA5CC-0B40-11D7-9779-00039396EEB8@apple.com \
    --to=klee@apple.com \
    --cc=binutils@sources.redhat.com \
    --cc=eliz@is.elta.co.il \
    --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