[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: some design issues
From: |
Marco Gerards |
Subject: |
Re: some design issues |
Date: |
Tue, 15 Feb 2005 19:41:56 +0000 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) |
"Yoshinori K. Okuji" <address@hidden> writes:
> I think the name "menu.lst" is really strange, so I don't like it. But I
> don't know if grub.cfg is nice. What do you think? I sometimes think
> that "grubrc" might be better (like "bashrc").
I like grub.cfg.
> Next thing. I think it is a bad idea to make the variable for a menu
> global, because this is not compatible with having multiple nested
> menus. But some commands want to access information on the environment
> (such as current menu). I can think of two ways to address this issue:
>
> 1. Pass one more argument to each command. This argument would be a
> pointer to struct context, and contains a pointer to current menu, etc.
>
> 2. Provide global functions to access information. These functions would
> have to use global variables.
With 2 you mean that the function accesses the current menu all the
time? Is accessing another menu useful in some cases?
Thanks,