From: Gaius Mulley <gaius@glam.ac.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Enhanced language support for Modula-2
Date: Thu, 16 Feb 2006 11:11:00 -0000 [thread overview]
Message-ID: <87zmkr5zj4.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <ud5hnj50l.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> > From: Gaius Mulley <gaius@glam.ac.uk>
> > Date: 15 Feb 2006 23:14:32 +0000
> >
> > Anyhow this patch provides better support for Modula-2 in the
> > following areas:
> >
> > * basic types are printed correctly when -gdwarf-2 is specified
> > on the gm2 command line.
> > * set types are supported (type printing and value printing).
> > The patch correctly identifies: SET OF CHAR, SET OF ['a'..'z']
> > etc.
> > * long and short (word length) sets are supported.
> > * range types are also identified and `ptype' prints them correctly.
> > * automatic detection of Modula-2 generated executable is enabled.
> > * VAR parameters are printed correctly
> > * hexadecimal addresses are written using the Modula-2 syntax.
> > * character constants are written using the octal syntax
> > (in the same way as PIM-[234].)
>
> Thanks.
>
> I think some of these changes might need updates in the user's manual.
> Could you please look at the "Modula-2" section and its subsections,
> and see if anything there should be added/removed/modified?
yes sure..
> > + error ("type not handled in m2_type_print_varspec_prefix()");
>
> User messages should be in _(), to allow for translations into other
> languages.
ok thanks for these pointers..
> > + fprintf_filtered(stream, "SET OF <unknown> ");
>
> "SET OF" probably won't be translated, but "<unknown>" should, so this
> message should be in _() as well.
true, I'll improve the patches and repost,
Gaius
next prev parent reply other threads:[~2006-02-16 11:11 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
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 [this message]
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=87zmkr5zj4.fsf@j228-gm.comp.glam.ac.uk \
--to=gaius@glam.ac.uk \
--cc=eliz@gnu.org \
--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