From: "Eli Zaretskii" <eliz@gnu.org>
To: Jason Molenda <jmolenda@apple.com>
Cc: gdb-patches@sources.redhat.com, jimb@redhat.com,
kettenis@jive.nl, dpatel@apple.com
Subject: Re: RFA/patch stabs reader: Recognize language hint in SO stab
Date: Fri, 06 Aug 2004 08:54:00 -0000 [thread overview]
Message-ID: <7137-Fri06Aug2004115131+0300-eliz@gnu.org> (raw)
In-Reply-To: <4F2AF76A-E71B-11D8-B4BD-000A9569836A@apple.com> (message from Jason Molenda on Thu, 5 Aug 2004 13:09:08 -0700)
> From: Jason Molenda <jmolenda@apple.com>
> Date: Thu, 5 Aug 2004 13:09:08 -0700
>
> Eli, I added a table documenting these values to stabs.texinfo. Do you
> think this is a correct use of a texinfo table?
It is correct usage, if what you want in the result is this:
`0x1 N_SO_AS'
Assembly language
`0x2 N_SO_C'
K&R traditional C
`0x3 N_SO_ANSI_C'
ANSI C
In other words, "@table @code" typesets the entire argument of each
@item in the @code face (in Info, that is emulated by enclosing it in
single quotes), and indents the text after the @item line by 4 spaces.
Therefore, if the indentation and the general formatting of @table is
okay with you, I think the following will look better:
+@table @asis
+@item @code{N_SO_AS} (0x1)
+Assembly language
+@item @code{N_SO_C} (0x2)
+K&R traditional C
etc., you get the point. This typesets only the N_SO_* symbols as
@code, and also emphasizes the symbolic names rather than the numeric
values, which I think is what we want.
Thanks.
next prev parent reply other threads:[~2004-08-06 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 20:08 Jason Molenda
2004-08-05 20:17 ` Jason Molenda
2004-08-05 20:55 ` Andrew Cagney
2004-08-24 20:45 ` Andrew Cagney
2004-08-25 1:05 ` Jason Molenda
2004-08-05 21:10 ` Michael Chastain
2004-08-06 8:54 ` Eli Zaretskii [this message]
2004-09-20 19:28 ` RFA/doc-patch " Jason Molenda
2004-09-21 3:43 ` Eli Zaretskii
2004-09-21 21:08 ` COMMITTED/doc-patch " Jason Molenda
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=7137-Fri06Aug2004115131+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=dpatel@apple.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=jmolenda@apple.com \
--cc=kettenis@jive.nl \
/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