All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Build failures on Ubuntu due to gettext
Date: Thu, 10 Dec 2009 02:10:19 +0100	[thread overview]
Message-ID: <20091210011019.GD15546@thorin> (raw)
In-Reply-To: <20091208001033.GQ6439@riva.ucam.org>

On Tue, Dec 08, 2009 at 12:10:34AM +0000, Colin Watson wrote:
> 
> My patch made the following transformation:
> 
> -  grub_printf (_("literal string"));
> +  grub_printf ("%s", _("literal string"));
> 
> This was only necessary in five places, so I doubt that a function is
> worth it.

I think we all agree that it's safer to avoid gettextizing the template;
furthemore I agree with Colin that this seems to be a correct approach,
but our case is unusual in that we're very pressed for size.

Even if we're only discussing a change in five places, I assume we're
going to find this situation in lots of calls throurough GRUB code.  If
this is so, it really calls for a solution that doesn't make GCC generate
two memory references and pass two arguments.

So first of all, how many times are we going to find similar calls that
need to be adjusted in some way?  If we're going to find many of them (as
I expect), I think this warrants adding a new function (which, btw, will
also make GRUB slightly faster).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  parent reply	other threads:[~2009-12-10  1:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 14:09 Build failures on Ubuntu due to gettext Colin Watson
2009-12-07 20:14 ` Carles Pina i Estany
2009-12-07 20:54   ` Colin Watson
2009-12-07 22:46     ` Carles Pina i Estany
2009-12-07 23:25       ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 23:57         ` Colin Watson
2009-12-07 23:38       ` Carles Pina i Estany
2009-12-07 23:59         ` Colin Watson
2009-12-08  0:00       ` Colin Watson
2009-12-08  0:14         ` Carles Pina i Estany
2009-12-07 22:04 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 23:12   ` Colin Watson
2009-12-07 23:38     ` Colin Watson
2009-12-07 23:59       ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-08  0:10         ` Colin Watson
2009-12-08  0:15           ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-09 23:57             ` Carles Pina i Estany
2009-12-10  0:07               ` Carles Pina i Estany
2009-12-10  0:38                 ` Carles Pina i Estany
2009-12-10  1:10           ` Robert Millan [this message]
2009-12-11  0:04             ` Carles Pina i Estany
2009-12-07 23:18   ` Carles Pina i Estany

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=20091210011019.GD15546@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.