From: "Jim Blandy" <jimb@red-bean.com>
To: "Gaius Mulley" <gaius@glam.ac.uk>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Enhanced language support for Modula-2
Date: Tue, 21 Feb 2006 19:21:00 -0000 [thread overview]
Message-ID: <8f2776cb0602211101u6917eb7bx9caa0bc7a7ecee41@mail.gmail.com> (raw)
In-Reply-To: <87lkw5qaa9.fsf@j228-gm.comp.glam.ac.uk>
On 21 Feb 2006 10:24:46 +0000, Gaius Mulley <gaius@glam.ac.uk> wrote:
> +Currently @value{GDBN} can print the following data types in Modula-2
> +syntax: array types, record types, set types, pointer types,
> +procedure types, enumerated types, subrange types and base types.
> +Values of these types may also be printed. So for example, if the
> +following section of code were compiled,
This is Eli's call, but it's general practice in GNU documentation to
go ahead and use "you" in preference to the passive voice. I don't
have a reference for this rule, I just have memories of Stallman
correcting this in my own writing. So the text above could be:
So for example, if you compile the following section of code:
> +@value{GDBN} could be requested to interrogate the type and value of
> +@code{r} and @code{s}.
Similarly:
you could request @value{GDBN} to interrogate the type and value of ...
> +the user can query the type of @code{s} via:
"you can query..."
> +Note that at present @value{GDBN} does not support interactive
> +manipulation of set expressions. However the debugger does understand
> +the declaration of Modula-2 arrays. For example in this code fragment
> +the declaration of @code{s} is described.
"For example, this code fragment describes the declaration of @code{s}:"
> +and this information is now seen by @value{GDBN}
"and @value{GDBN} now sees this information"
and so on.
next prev parent reply other threads:[~2006-02-21 19:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 23:15 Gaius Mulley
2006-02-16 0:20 ` Jim Blandy
2006-02-16 11:06 ` Gaius Mulley
2006-02-20 15:05 ` Daniel Jacobowitz
2006-02-20 21:42 ` Jim Blandy
2006-02-21 11:06 ` Gaius Mulley
2006-02-21 19:01 ` Jim Blandy
2006-02-25 13:17 ` Gaius Mulley
2006-02-26 5:44 ` Jim Blandy
2006-02-26 5:46 ` Daniel Jacobowitz
2006-02-28 5:37 ` Gaius Mulley
2006-02-28 13:53 ` Jim Blandy
2006-03-02 8:57 ` Gaius Mulley
2006-03-02 17:27 ` Jim Blandy
2006-02-21 19:21 ` Jim Blandy [this message]
2006-02-21 20:51 ` Eli Zaretskii
2006-02-21 20:50 ` Eli Zaretskii
2006-02-21 20:57 ` Mark Kettenis
2006-02-22 5:33 ` Eli Zaretskii
2006-02-22 18:36 ` Eli Zaretskii
2006-02-16 4:34 ` Eli Zaretskii
2006-02-16 11:11 ` Gaius Mulley
2006-04-20 13:23 Gaius Mulley
2006-04-20 14:35 ` Eli Zaretskii
2006-04-20 18:47 ` Mark Kettenis
2006-04-20 18:54 ` Eli Zaretskii
2006-05-04 7:17 ` Gaius Mulley
2006-05-04 15:37 ` Daniel Jacobowitz
2006-05-04 18:01 ` Jim Blandy
2006-05-08 14:09 ` Gaius Mulley
2006-05-08 17:47 ` Jim Blandy
2006-05-09 22:57 ` Gaius Mulley
2006-05-10 21:45 ` Jim Blandy
2006-05-11 12:37 ` Gaius Mulley
2006-05-12 18:18 ` Joel Brobecker
2006-05-12 18:27 ` Jim Blandy
2006-05-13 13:31 ` Gaius Mulley
2006-05-13 11:02 ` Gaius Mulley
2006-05-08 21:03 ` Eli Zaretskii
2006-05-04 16:12 ` 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=8f2776cb0602211101u6917eb7bx9caa0bc7a7ecee41@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gaius@glam.ac.uk \
--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