public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marco Poletti <poletti.marco@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Paolo Bonzini <bonzini@gnu.org>,
	"Joseph S. Myers" <joseph@codesourcery.com>,
	 	gdr@integrable-solutions.net,
	Gabriel Dos Reis <dosreis@gmail.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: gcc/cp/pt.c: use ngettext() when needed
Date: Mon, 22 Feb 2010 09:38:00 -0000	[thread overview]
Message-ID: <ae2276fe1002220125m9189b02g98e6279a381fd4b3@mail.gmail.com> (raw)
In-Reply-To: <ae2276fe1002180649v5d717bf6t28a8c98c458a130d@mail.gmail.com>

2010/2/18 Marco Poletti <poletti.marco@gmail.com>:
> 2010/2/18 Jakub Jelinek <jakub@redhat.com>:
>> On Thu, Feb 18, 2010 at 03:33:34PM +0100, Marco Poletti wrote:
>>> --- gcc/diagnostic.c  (revisione 156858)
>>> +++ gcc/diagnostic.c  (copia locale)
>>> @@ -519,6 +519,23 @@ inform (location_t location, const char
>>>    va_end (ap);
>>>  }
>>>
>>> +/* An informative note at LOCATION.  Use this for additional details
>>> on an error
>>
>> Too long line.
>>
>>> +   message. The message is already translated.  */
>>
>> The message is not translated, inform_n does the translation.
>>
>>> +/* A hard error: the code is definitely ill-formed, and an object file
>>> +   will not be produced. The message is already translated.  */
>>
>> Likewise.
>>
>>        Jakub
>>
>
> @Jakub:
> Yes, you're right. Thanks for pointing these out.
>
> Updated patch:
>
> Index: gcc/diagnostic.c
> ===================================================================
> --- gcc/diagnostic.c    (revisione 156858)
> +++ gcc/diagnostic.c    (copia locale)
> @@ -519,6 +519,23 @@ inform (location_t location, const char
>   va_end (ap);
>  }
>
> +/* An informative note at LOCATION.  Use this for additional details on an
> +   error message.  */
> +void
> +inform_n (location_t location, int n, const char *singular_gmsgid,
> +          const char *plural_gmsgid, ...)
> +{
> +  diagnostic_info diagnostic;
> +  va_list ap;
> +
> +  va_start (ap, plural_gmsgid);
> +  diagnostic_set_info_translated (&diagnostic,
> +                                  ngettext (singular_gmsgid, plural_gmsgid, n),
> +                                  &ap, location, DK_NOTE);
> +  report_diagnostic (&diagnostic);
> +  va_end (ap);
> +}
> +
>  /* A warning at INPUT_LOCATION.  Use this for code which is correct according
>    to the relevant language specification but is likely to be buggy anyway.
>    Returns true if the warning was printed, false if it was inhibited.  */
> @@ -613,6 +630,23 @@ error (const char *gmsgid, ...)
>   report_diagnostic (&diagnostic);
>   va_end (ap);
>  }
> +
> +/* A hard error: the code is definitely ill-formed, and an object file
> +   will not be produced.  */
> +void
> +error_n (location_t location, int n, const char *singular_gmsgid,
> +         const char *plural_gmsgid, ...)
> +{
> +  diagnostic_info diagnostic;
> +  va_list ap;
> +
> +  va_start (ap, plural_gmsgid);
> +  diagnostic_set_info_translated (&diagnostic,
> +                                  ngettext (singular_gmsgid, plural_gmsgid, n),
> +                                  &ap, location, DK_ERROR);
> +  report_diagnostic (&diagnostic);
> +  va_end (ap);
> +}
>
>  /* Same as ebove, but use location LOC instead of input_location.  */
>  void
> Index: gcc/toplev.h
> ===================================================================
> --- gcc/toplev.h        (revisione 156858)
> +++ gcc/toplev.h        (copia locale)
> @@ -63,6 +63,8 @@ extern bool warning (int, const char *,
>  extern bool warning_at (location_t, int, const char *, ...)
>     ATTRIBUTE_GCC_DIAG(3,4);
>  extern void error (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
> +extern void error_n (location_t, int, const char *, const char *, ...)
> +    ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
>  extern void error_at (location_t, const char *, ...) ATTRIBUTE_GCC_DIAG(2,3);
>  extern void fatal_error (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2)
>      ATTRIBUTE_NORETURN;
> @@ -72,6 +74,8 @@ extern bool pedwarn (location_t, int, co
>  extern bool permerror (location_t, const char *, ...) ATTRIBUTE_GCC_DIAG(2,3);
>  extern void sorry (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
>  extern void inform (location_t, const char *, ...) ATTRIBUTE_GCC_DIAG(2,3);
> +extern void inform_n (location_t, int, const char *, const char *, ...)
> +    ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
>  extern void verbatim (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
>
>  extern void rest_of_decl_compilation (tree, int, int);
> Index: gcc/cp/pt.c
> ===================================================================
> --- gcc/cp/pt.c (revisione 156858)
> +++ gcc/cp/pt.c (copia locale)
> @@ -4614,10 +4614,14 @@ redeclare_class_template (tree type, tre
>
>   if (TREE_VEC_LENGTH (parms) != TREE_VEC_LENGTH (tmpl_parms))
>     {
> -      error ("redeclared with %d template parameter(s)",
> -             TREE_VEC_LENGTH (parms));
> -      inform (input_location, "previous declaration %q+D used %d
> template parameter(s)",
> -             tmpl, TREE_VEC_LENGTH (tmpl_parms));
> +      error_n (input_location, TREE_VEC_LENGTH (parms),
> +               "redeclared with %d template parameter",
> +               "redeclared with %d template parameters",
> +               TREE_VEC_LENGTH (parms));
> +      inform_n (input_location, TREE_VEC_LENGTH (tmpl_parms),
> +                "previous declaration %q+D used %d template parameter",
> +                "previous declaration %q+D used %d template parameters",
> +                tmpl, TREE_VEC_LENGTH (tmpl_parms));
>       return false;
>     }
>
> Index: gcc/po/exgettext
> ===================================================================
> --- gcc/po/exgettext    (revisione 156858)
> +++ gcc/po/exgettext    (copia locale)
> @@ -112,6 +112,8 @@ function keyword_option(line) {
>     else if (args ~ /c$/)
>        format="c-format"
>
> +    if (name ~ /_n$/) n = n "," (n + 1)
> +
>     if (n == 1) { keyword = "--keyword=" name }
>     else { keyword = "--keyword=" name ":" n }
>     if (format) {
>


PING!
Can someone comment on this or commit it?


Marco Poletti

  reply	other threads:[~2010-02-22  9:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 15:23 Marco Poletti
2010-02-17 15:25 ` Marco Poletti
2010-02-17 17:06 ` Gabriel Dos Reis
2010-02-17 18:02   ` Marco Poletti
2010-02-17 18:29   ` Paolo Bonzini
2010-02-17 20:07     ` Marco Poletti
2010-02-17 21:26     ` Joseph S. Myers
2010-02-17 21:32       ` Marco Poletti
2010-02-17 23:23         ` Paolo Bonzini
2010-02-18 14:33           ` Marco Poletti
2010-02-18 14:40             ` Jakub Jelinek
2010-02-18 14:49               ` Marco Poletti
2010-02-22  9:38                 ` Marco Poletti [this message]
2010-02-24  6:47                   ` Shujing Zhao
2010-02-24  6:57                     ` Paolo Bonzini
2010-02-24  8:55                       ` Shujing Zhao
2010-02-24 10:22                         ` Paolo Bonzini
2010-02-26  7:30                     ` Gabriel Dos Reis
2010-02-26  7:31                       ` Marco Poletti
2010-02-26  9:32                         ` Gabriel Dos Reis
2010-02-26  9:43                           ` Paolo Bonzini
2010-02-26  9:56                             ` Gabriel Dos Reis
2010-02-26 10:03                               ` Jakub Jelinek
2010-02-26 10:04                                 ` Gabriel Dos Reis
2010-02-26 10:09                                   ` Shujing Zhao
2010-02-26 10:42                                     ` Paolo Bonzini
2010-02-26 10:43                                       ` Jakub Jelinek
2010-03-01 10:00                                         ` Shujing Zhao
2010-03-01 10:16                                           ` Shujing Zhao
2010-03-01 15:12                                             ` Gabriel Dos Reis

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=ae2276fe1002220125m9189b02g98e6279a381fd4b3@mail.gmail.com \
    --to=poletti.marco@gmail.com \
    --cc=bonzini@gnu.org \
    --cc=dosreis@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).