From: Kevin Lacquement <kevin@lacqui.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Menus and Functions
Date: Mon, 02 Mar 2009 11:22:25 -0800 [thread overview]
Message-ID: <49AC31F1.6020806@lacqui.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greetings all,
I was browsing through the recent SVN head, and noticed that functions
and menu items are implemented separately. I was wondering if there's
actually a reason for that.
It seems to me that a menu entry is nothing more than a function that,
instead of being referred to by a function name, is referred to by a
menu title.
Would it be difficult to re-implement menu entries to hold a function
pointer? This should simplify the scripting engine, as it can all be
put into one place.
Cheers,
Kevin
- --
Sic non confunctus, non reficiat.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkmsMfEACgkQASQ0HFKCohNQYACfSs1SNshxsp/nD8S/yqZL3/f2
kVwAoIG4JEJIXp2Oqc4pTAHytfvdkusb
=ANIt
-----END PGP SIGNATURE-----
next reply other threads:[~2009-03-02 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 19:22 Kevin Lacquement [this message]
2009-03-03 20:07 ` Menus and Functions Marco Gerards
2009-03-04 2:22 ` Kevin Lacquement
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=49AC31F1.6020806@lacqui.com \
--to=kevin@lacqui.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.