All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] UUID support for UFS
Date: Tue, 21 Jul 2009 22:14:02 +0200	[thread overview]
Message-ID: <4A66218A.3020506@gmail.com> (raw)
In-Reply-To: <1248213902.18091.20.camel@mj>

Pavel Roskin escribió:
> On Tue, 2009-07-21 at 23:45 +0200, Vladimir 'phcoder' Serbinenko wrote:
> 
>> This change would allow to produce a code which is cleaner, easier to
>> read and understand. However I'm opposed to modifying printf function
>> for it.
> 
> I think Javier misspoke or didn't realize that *printf doesn't need to
> be modified.
Indeed, I didn't realise so. All that's required is a grub_inttypes 
header that either takes from the system stdint.h types or just defines 
the macros you were discussing.
> 
>>  Instead we could just define somewhere:
>> GRUB_PRIx32 "%x"
> 
> Better yet, "x", as in libc.  That would allow for "%08x" that we need
> for UUID.
Yeah, that is the format used in libc. I copied the example wrong, 
without the "%08"s.
> 
> But I would prefer that we work on fixing bugs rather than non-bugs.
> 
"Fixing" this would allow us to have cleaner code, and separate "casual 
variables" from fixed-length variables. If we print int with %d and 
int32_t with PRId32, the impact of the subtle bugs that appear when we 
port across architectures will be reduced.




  reply	other threads:[~2009-07-21 22:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 13:03 [PATCH] UUID support for UFS Vladimir 'phcoder' Serbinenko
2009-07-21 17:14 ` Pavel Roskin
2009-07-21 20:01   ` Vladimir 'phcoder' Serbinenko
2009-07-21 18:46     ` Javier Martín
2009-07-21 21:31       ` Pavel Roskin
2009-07-21 21:45         ` Vladimir 'phcoder' Serbinenko
2009-07-21 22:05           ` Pavel Roskin
2009-07-21 20:14             ` Javier Martín [this message]
2009-07-21 22:37               ` Pavel Roskin
2009-07-21 21:34                 ` Javier Martín
2009-07-22  0:20                   ` Pavel Roskin
2009-07-22 17:47                   ` Robert Millan
2009-07-22 18:02                     ` Javier Martín
2009-07-22 17:44           ` Robert Millan
2009-07-21 20:04     ` Pavel Roskin
2009-07-22 17:40 ` Robert Millan
2009-07-22 17:47   ` Vladimir 'phcoder' Serbinenko
2009-07-22 18:01   ` Pavel Roskin

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=4A66218A.3020506@gmail.com \
    --to=lordhabbit@gmail.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.