public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: law@cygnus.com, binutils@sourceware.cygnus.com, richard.earnshaw@arm.com
Subject: Re: Minor arm cleanup
Date: Mon, 01 Nov 1999 15:35:00 -0000	[thread overview]
Message-ID: <jek8o17plh.fsf@hawking.suse.de> (raw)
In-Reply-To: <199910280906.KAA24085@cam-mail1.cambridge.arm.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

Richard Earnshaw <rearnsha@arm.com> writes:

|> > 
|> > We generally frown upon lower-case macros.
|> > 
|> > This change changes the bad_pc and bad_args macros to be upper case.  That's
|> > it.
|> > 
|> > 	* tc-arm.c (bad_args, bad_pc): Renamed to BAD_ARGS and BAD_PC
|> > 	respectively.
|> 
|> Hmm, When I wrote this originally, bad_args and bad_pc were variables, so 
|> that compilers (eg sparcworks) that didn't put strings into read-only 
|> sections wouldn't generate dozens of duplicate strings.  My guess is that 
|> with the change to internationalize the strings this "optimization" was 
|> lost.

I'd guess the problem was that bad_args and bad_pc were global variables,
initialized with the string, which does not work as such with gettext (you
have to translate at runtime).

You can restore the old behaviour by using the N_ macro to mark the string
at file scope, and put _() around every use of the variables.  But then,
it's probably not worth the hassle.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg

      reply	other threads:[~1999-11-01 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27 15:54 Jeffrey A Law
1999-10-28  2:06 ` Richard Earnshaw
1999-11-01 15:35   ` Andreas Schwab [this message]

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=jek8o17plh.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=binutils@sourceware.cygnus.com \
    --cc=law@cygnus.com \
    --cc=rearnsha@arm.com \
    --cc=richard.earnshaw@arm.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).