From: Kevin Buettner <kevinb@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA/RFC] Address class support
Date: Thu, 17 Oct 2002 11:15:00 -0000 [thread overview]
Message-ID: <1021017181453.ZM32336@localhost.localdomain> (raw)
In-Reply-To: Eli Zaretskii <eliz@is.elta.co.il> "Re: [PATCH RFA/RFC] Address class support" (Oct 17, 8:39am)
On Oct 17, 8:39am, Eli Zaretskii wrote:
> Approved, with the following comments/suggestions:
>
> > +@deftypefn {Target Macro} int ADDRESS_CLASS_TYPE_FLAGS (int @var{byte_size}, int @var{dwarf2_addr_class})
>
> Do you really need to use @var inside deftypefn (I don't have the Texinfo
> manual handy, sorry)? I thought the @def... directives supply the @var
> automatically.
According to the texinfo manual, an explicit @var is needed For deftypefn:
The argument names that you write in @deftypefn are not subject to
an implicit @var--since the actual names of the arguments in
@deftypefn are typically scattered among data type names and
keywords, Texinfo cannot find them without help. Instead, you
must write @var explicitly around the argument names. In the
example above, the argument names are foo and bar.
(I didn't know this ahead of time though; I was just following the
example set by the rest of the manual.)
> > +Consider a hypothetical architecture in which addresses are normally
> > +32-bits wide, but 16-bit addresses are also supported. Furthermore,
> > +suppose that the DWARF 2 information for this architecture simply
>
> I suggest to use either DWARF2 or @w{DWARF 2}, to prevent TeX and makeinfo
> from splitting this between DWARF and 2.
I'll use @w{DWARF 2} for consistency with the rest of the manual. (There
are some other places that need to be fixed though.)
> > +@smallexample
> > +somearch_address_class_type_flags (int byte_size, int dwarf2_addr_class)
>
> This line is too long (even for @smallexample), so please break it in
> two:
>
> +somearch_address_class_type_flags (int byte_size,
> + int dwarf2_addr_class)
>
> (There are more too long lines in your examples. In general, any line
> inside @smallexample that is longer than 64 characters should be broken
> into several lines, or else it will cause overfull hbox'es when you TeX
> the manual.)
Okay, fixed.
Thanks for your help.
Kevin
next prev parent reply other threads:[~2002-10-17 18:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 17:42 Kevin Buettner
2002-10-16 0:24 ` Jim Blandy
2002-10-16 23:39 ` Eli Zaretskii
2002-10-17 11:15 ` Kevin Buettner [this message]
2002-10-16 11:42 ` Kevin Buettner
2002-10-16 23:39 ` Eli Zaretskii
[not found] ` <eliz@is.elta.co.il>
2002-10-17 12:23 ` Kevin Buettner
2002-10-16 13:57 ` Kevin Buettner
2002-10-21 16:49 ` Andrew Cagney
2002-11-27 20:32 ` Andrew Cagney
2002-12-02 6:52 ` Kevin Buettner
2002-12-09 15:42 ` Kevin Buettner
2002-12-11 12:32 ` Kevin Buettner
2002-10-22 7:10 ` Andrew Cagney
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=1021017181453.ZM32336@localhost.localdomain \
--to=kevinb@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