This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] Add stabs entries for coalesced symbols.

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
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?

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]