From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot2: make multiboot header optional
Date: Tue, 12 Dec 2006 23:08:26 +0100 [thread overview]
Message-ID: <200612122308.26778.okuji@enbug.org> (raw)
In-Reply-To: <1165531179.8900.24.camel@basalt>
On Thursday 07 December 2006 23:39, Hollis Blanchard wrote:
> I thought we had two options: embedding tags, or ORing bits into an
> embedded long. When I suggested embedding tags, you told me it was too
> complicated so will cause developer errors. Have I misunderstood?
I meant that the complexity of using bitfields plus a fixed-size structure is
identical to that of using tags. But I bet that it is more complicated to use
tags _by hand_. For me, "complex" and "complicated" are quite different.
Besides how to make it look easier by predefined macros, please consider the
spec itself. With bitfields and fixed-size fields, all you must remember is:
- What bits mean what
- How to order values passed to a boot loader
With tags, you need to remember:
- What tags mean what
- What tag size is expected to each tag
- What tags must be combined with a given tag
If you generate tags by programming, I don't think the use of tags is more
complicated. It can be even easier for a parser. However, when specifying
tags by hand, I cannot believe that it is as straightforward as using fields.
If you allow me to use a "big gun", I would tell you that most system
programmers are used to fields, while they are not familar with writing tags.
Okuji
next prev parent reply other threads:[~2006-12-12 22:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 22:58 multiboot2: make multiboot header optional Hollis Blanchard
2006-11-15 8:57 ` Johan Rydberg
2006-11-15 18:42 ` Hollis Blanchard
2006-11-15 20:42 ` Yoshinori K. Okuji
2006-11-15 21:39 ` Hollis Blanchard
2006-11-15 23:38 ` tgingold
2006-11-25 2:59 ` Yoshinori K. Okuji
2006-11-25 3:35 ` Hollis Blanchard
2006-11-25 4:25 ` Yoshinori K. Okuji
2006-12-02 16:18 ` Marco Gerards
2006-12-02 17:27 ` Yoshinori K. Okuji
2006-12-04 16:43 ` Hollis Blanchard
2006-12-05 20:23 ` Yoshinori K. Okuji
2006-12-07 23:07 ` multiboot2: using tags in the multiboot header Hollis Blanchard
2006-12-12 22:23 ` Yoshinori K. Okuji
2006-12-04 20:35 ` multiboot2: make multiboot header optional Marco Gerards
2006-12-05 19:09 ` Hollis Blanchard
2006-12-05 20:04 ` Yoshinori K. Okuji
2006-12-07 22:39 ` Hollis Blanchard
2006-12-12 22:08 ` Yoshinori K. Okuji [this message]
2006-12-13 4:18 ` Hollis Blanchard
2006-12-13 20:56 ` Yoshinori K. Okuji
2006-12-13 12:28 ` Marco Gerards
2006-12-02 16:15 ` Marco Gerards
2006-12-02 17:19 ` Yoshinori K. Okuji
2006-11-15 20:37 ` Yoshinori K. Okuji
2006-11-15 23:41 ` tgingold
2006-11-21 16:18 ` Hollis Blanchard
2006-11-21 17:35 ` tgingold
2006-11-25 3:05 ` Yoshinori K. Okuji
2006-11-25 3:00 ` Yoshinori K. Okuji
2006-11-25 6:12 ` Tristan Gingold
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=200612122308.26778.okuji@enbug.org \
--to=okuji@enbug.org \
--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.