From: Johan Rydberg <jrydberg@night.trouble.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] generic ELF loading #3
Date: Wed, 01 Nov 2006 13:48:36 +0100 [thread overview]
Message-ID: <87ejsnxrh7.fsf@night.trouble.net> (raw)
In-Reply-To: <1162344225.8547.81.camel@basalt.austin.ibm.com> (Hollis Blanchard's message of "Tue, 31 Oct 2006 19:23:45 -0600")
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Hollis Blanchard <hollis@penguinppc.org> writes:
> --- grub2-cvs.orig/include/grub/types.h 2006-10-31 19:06:47.000000000 -0600
> +++ grub2-cvs/include/grub/types.h 2006-10-31 19:06:58.000000000 -0600
> @@ -23,6 +23,8 @@
> #include <config.h>
> #include <grub/cpu/types.h>
>
> +#define __unused __attribute__ ((unused))
> +
First when I saw this it made me wanna comment on it, and tell you
that defines should all be in uppercase. But then I poked through the
code, and saw the usage of it, and it looked quite nice, with the
exception of the __-prefix. There are a lot of "common" words that
are keywords in C; inline, const and auto for example. Maybe we
should make "unused" a reserved keyword in GRUB? That would allow
us to write code like;
int
grub_foo (int x, unused int foo)
{
...
}
Just a thought. Otherwise your patch looked just fine Hollis.
~j
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2006-11-01 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 1:23 [PATCH] generic ELF loading #3 Hollis Blanchard
2006-11-01 12:48 ` Johan Rydberg [this message]
2006-11-03 20:45 ` __unused Hollis Blanchard
2006-11-04 3:44 ` __unused Johan Rydberg
2006-11-08 23:10 ` __unused Jeroen Dekkers
2006-11-09 15:31 ` __unused Johan Rydberg
2006-11-09 19:42 ` __unused Jeroen Dekkers
2006-11-02 19:58 ` [PATCH] generic ELF loading #3 Yoshinori K. Okuji
2006-11-02 20:54 ` Hollis Blanchard
2006-11-02 21:23 ` Hollis Blanchard
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=87ejsnxrh7.fsf@night.trouble.net \
--to=jrydberg@night.trouble.net \
--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.