From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB integral types? Why grub_uint32_t and not uint32_t?
Date: Thu, 29 May 2008 18:39:53 +0200 [thread overview]
Message-ID: <20080529163953.GA21784@thorin> (raw)
In-Reply-To: <20080529085756.43310531@gibibit.com>
On Thu, May 29, 2008 at 08:57:56AM -0700, Colin D Bennett wrote:
> I was wondering why it is necessary to use the integral types with
> the "grub_" prefix instead of the standard uint32_t, int16_t, etc.?
>
> It makes the most simple code much more verbose when we have to write
> "grub_" so many times, and this seems like a case where it is not
> needed.
It makes our code more consistent and less prone to errors. This is more
relevant for freestanding code like GRUB than it'd be for a user program.
For an example, you can check the list archives and find how system headers
in different OSes break GRUB in different interesting and fun ways ;-)
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)
prev parent reply other threads:[~2008-05-29 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 15:57 GRUB integral types? Why grub_uint32_t and not uint32_t? Colin D Bennett
2008-05-29 16:39 ` Robert Millan [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=20080529163953.GA21784@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.