From: Eli Zaretskii <eliz@is.elta.co.il>
To: David Carlton <carlton@math.stanford.edu>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc] correct info about best C++ compilers/debug formats
Date: Tue, 04 Feb 2003 06:08:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1030204075821.22830D-100000@is> (raw)
In-Reply-To: <ro1lm0x86kv.fsf@jackfruit.Stanford.EDU>
On 3 Feb 2003, David Carlton wrote:
> I can go with that. I would assume that the + in 'stabs+' has to be
> set off by @t, but TeXinfo doesn't complain; Eli, should I use stabs+
> or stabs@t{+}?
I'd use either @code{stabs+} or simply stabs+. The @t{++} in C@t{++} is
a kind of gimmick, since the C++ language name is a pun on a C operator
++. There's no such pun in stabs+, AFAIK.
> Here's the next version of the patch; it changes this sentence, and
> also replaces some uses of @samp{-gsomething} by @option{-gsomething},
> which I assume is preferred.
Yes, @option is preferred once we require Texinfo 4.0 or later.
> +an effective form for debug info. See @ref{Debugging Options,,Options
> +for Debugging Your Program or @sc{gnu} CC, gcc.info, Using @sc{gnu} CC},
> +for more information.
It is better to use "@xref{something}" rather than "See @ref{something}"
at the beginning of a sentence, since the result will look better in Info
(a single "*Note" instead of a "See *note"). Sorry I didn't catch this
earlier.
Otherwise, this is fine; please go ahead and commit it.
Thanks.
next prev parent reply other threads:[~2003-02-04 6:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302032008.h13K8M230404@duracef.shout.net>
2003-02-03 20:14 ` David Carlton
2003-02-04 6:08 ` Eli Zaretskii [this message]
2003-02-04 7:04 ` Andrew Cagney
2003-02-04 21:17 ` David Carlton
2003-02-05 5:54 ` Eli Zaretskii
2003-02-04 14:41 Michael Elizabeth Chastain
-- strict thread matches above, loose matches on Subject: below --
2003-02-04 6:24 Michael Elizabeth Chastain
2003-02-04 8:08 ` Eli Zaretskii
2003-02-03 21:21 Michael Elizabeth Chastain
2003-02-04 6:16 ` Eli Zaretskii
2003-02-03 19:29 David Carlton
2003-02-03 18:27 David Carlton
2003-02-03 18:37 ` Daniel Jacobowitz
2003-02-03 19:23 ` Eli Zaretskii
2003-02-03 20:09 ` David Carlton
2003-02-03 20:49 ` Andrew Cagney
2003-02-04 6:14 ` Eli Zaretskii
2003-02-04 5:59 ` Eli Zaretskii
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=Pine.SUN.3.91.1030204075821.22830D-100000@is \
--to=eliz@is.elta.co.il \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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