From: Andrew Cagney <ac131313@cygnus.com>
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: gettextize jv-exp.y
Date: Tue, 25 Jun 2002 19:57:00 -0000 [thread overview]
Message-ID: <3D192D8C.7000308@cygnus.com> (raw)
In-Reply-To: <87bs9zhp7c.fsf@fleche.redhat.com>
> This patch gettextizes jv-exp.y.
>
> In this case one code change was required. Look at yyerror().
> Also I fixed a couple of typos while I was at it.
I would have ignored it but you mentioned fixing typos. Some more ..
>
> ClassInstanceCreationExpression:
> NEW ClassType '(' ArgumentList_opt ')'
> - { error ("FIXME - ClassInstanceCreationExpression"); }
> + { error (_("FIXME - ClassInstanceCreationExpression")); }
internal_error (_("..."));
> ArgumentList:
> @@ -408,9 +408,9 @@
>
> ArrayCreationExpression:
> NEW PrimitiveType DimExprs Dims_opt
> - { error ("FIXME - ArrayCreatiionExpression"); }
> + { error (_("FIXME - ArrayCreationExpression")); }
> | NEW ClassOrInterfaceType DimExprs Dims_opt
> - { error ("FIXME - ArrayCreatiionExpression"); }
> + { error (_("FIXME - ArrayCreationExpression")); }
Ditto.
> DimExprs:
> @@ -445,11 +445,11 @@
>
> MethodInvocation:
> Name '(' ArgumentList_opt ')'
> - { error ("method invocation not implemented"); }
> + { error (_("method invocation not implemented")); }
Leading capital letter in error message.
> | Primary '.' SimpleName '(' ArgumentList_opt ')'
> - { error ("method invocation not implemented"); }
> + { error (_("method invocation not implemented")); }
> | SUPER '.' SimpleName '(' ArgumentList_opt ')'
> - { error ("method invocation not implemented"); }
> + { error (_("method invocation not implemented")); }
> ;
Ditto.
> ArrayAccess:
> @@ -539,7 +539,7 @@
> int i;
> int base = expout_ptr - last_exp_size - 3;
> if (base < 0 || expout->elts[base+2].opcode != OP_TYPE)
> - error ("invalid cast expression");
> + error (_("invalid cast expression"));
Ditto.
> type = expout->elts[base+1].type;
> /* Remove the 'Expression' and slide the
> UnaryExpressionNotPlusMinus down to replace it. */
> @@ -795,7 +795,7 @@
> return ERROR;
> if (n > limit_div_base
> || (n *= base) > limit - c)
> - error ("Numeric constant too large.");
> + error (_("Numeric constant too large."));
I'm not 100% certain but I believe the intent, in GDB is for error
messages to not include the period?
> - error ("A %s in expression, near `%s'.", (msg ? msg : "error"), lexptr);
> + if (msg)
> + error (_("%s: near `%s'."), lexptr);
The above is wrong, shouldn't --enable-gdb-warnings=,-Werror be
detecting this? It includes -Wprintf.
Andrew
next prev parent reply other threads:[~2002-06-26 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 22:48 Tom Tromey
2002-06-25 10:11 ` Andrew Cagney
2002-06-25 19:57 ` Andrew Cagney [this message]
2002-07-24 9:22 ` Tom Tromey
2002-07-24 18:49 ` 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=3D192D8C.7000308@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@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