public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Philipp Thomas <pthomas@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: fortran/5558: Error in POT file
Date: Fri, 01 Feb 2002 13:56:00 -0000 [thread overview]
Message-ID: <20020201215601.16033.qmail@sources.redhat.com> (raw)
The following reply was made to PR fortran/5558; it has been noted by GNATS.
From: Philipp Thomas <pthomas@suse.de>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: toon@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
martin@v.loewis.de, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: fortran/5558: Error in POT file
Date: Fri, 1 Feb 2002 22:49:31 +0100
* Toon Moene (toon@moene.indiv.nluug.nl) [20020201 22:20]:
> The problem is caused by the fact that several "proto" error messages in
> the Fortran front-end have "printf"-like "%" sequences.
>
> However, they definitely are *not* printf format strings. Hence
> classifying them as c-format is wrong.
The solution is very easy. Before each of those lines put the comment
/* xgettext:no-c-format */
That will prevent xgettext ever mistakenly mark such a string as
printf-like. We could limit the marking to only those strings that xgettext
wrongly marked, but I'd say fix it once and for all.
Now who's going to do the dirty work, me or you? ;-)
Philipp
--
Philipp Thomas <pthomas@suse.de>
Development, SuSE Linux AG, Deutscherrnstr. 15-19, D-90429 Nuremberg, Germany
next reply other threads:[~2002-02-01 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 13:56 Philipp Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-04 15:29 pthomas
2002-02-01 16:16 Martin v. Loewis
2002-02-01 15:06 Philipp Thomas
2002-02-01 14:56 Toon Moene
2002-02-01 13:26 Toon Moene
2002-02-01 6:16 Philipp Thomas
2002-02-01 6:09 toon
2002-02-01 1:26 Martin v. Loewis
2002-01-31 17:06 Zack Weinberg
2002-01-31 16:36 Martin v. Loewis
2002-01-31 15:56 Zack Weinberg
2002-01-31 13:06 martin
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=20020201215601.16033.qmail@sources.redhat.com \
--to=pthomas@suse.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).