All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Include
Date: Sat, 29 Apr 2006 14:42:28 +0200	[thread overview]
Message-ID: <200604291442.29130.okuji@enbug.org> (raw)
In-Reply-To: <200604291404.57583.okuji@enbug.org>

Currently, the commands default, timeout, etc. are ad-hoc, because they can be 
usual variables, but they are commands only for the menu context. I think the 
right way is to make a context for variables (and maybe for funcions as 
well).

This can be implemented differently, that is, using handlers. Handlers can 
change the behavior of each variable arbitrarily. But I'm afraid that this is 
sometimes confusing, and could be a burden, if we want to define more 
menu-specific variables. For instance, I'm considering using variables to 
define a "theme" of the menu interface. This would require a lot of 
variables. If we use handlers, we would have so many special variables... 
IMO, handlers are exceptions, and less exceptions are better to understand 
the system.

So I'd like to make variables more similar to BASH's semantics; by default, 
all variables should be local, and become global only when the user executes 
"export". Then, a reference of a variable means that GRUB first search the 
variable in the current context, then in the global context. This looks 
cleaner than the current implementation.

Okuji



  parent reply	other threads:[~2006-04-29 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-29 11:42 Include Marco Gerards
2006-04-29 12:04 ` Include Yoshinori K. Okuji
2006-04-29 12:34   ` Include Marco Gerards
2006-04-29 12:42   ` Yoshinori K. Okuji [this message]
2006-04-29 13:02     ` Include Marco Gerards

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=200604291442.29130.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.