This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Enhanced language support for Modula-2


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]