Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch, doc RFA]: New python function lookup_global_symbol
Date: Thu, 24 Feb 2011 03:51:00 -0000	[thread overview]
Message-ID: <AANLkTikTXmUBXUkKPm9wKC=oEnDWRihYA-KR=O93rMFa@mail.gmail.com> (raw)
In-Reply-To: <83r5azs8me.fsf@gnu.org>

On Tue, Feb 22, 2011 at 8:00 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Tue, 22 Feb 2011 14:50:10 -0800
>> From: Doug Evans <dje@google.com>
>> Cc: gdb-patches@sourceware.org
>>
>> Thanks.
>> Here is what I checked in.
>
> One comment about your commit:
>
>> +is a field of a method's object (e.g., @code{this} in @code{C++}),
>
> We use "C@t{++}" in the manual for the C++ language.  Putting it all
> in @code is not right, because it isn't a program symbol, and it also
> looks weird in the Info output, where @code is converted to `..'
> quoted string.

Ah, right.  Sorry 'bout that.  Fixed.

I grepped for C++ trying to find the right way to write `C++', but of
course such a grep fails to find C@t{++}.  I wonder how useful it
would be to have a section at the top of the file containing various
formatting hints.


  reply	other threads:[~2011-02-23 23:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-19  1:04 Doug Evans
2011-02-19 10:37 ` Eli Zaretskii
2011-02-22 23:04   ` Doug Evans
2011-02-23  4:17     ` Eli Zaretskii
2011-02-24  3:51       ` Doug Evans [this message]
2011-02-24  4:14         ` Eli Zaretskii
2011-02-22 22:50 ` Tom Tromey

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='AANLkTikTXmUBXUkKPm9wKC=oEnDWRihYA-KR=O93rMFa@mail.gmail.com' \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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