From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Allow user-defined functions to override builtins.
Date: Thu, 22 May 2014 09:31:24 +0200 [thread overview]
Message-ID: <537DA7CC.8000507@gmail.com> (raw)
In-Reply-To: <20140519013715.1e36d215@crass-Ideapad-Z570>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On 19.05.2014 08:37, Glenn Washburn wrote:
> Currently, builtin commands take precedence over user-defined
> functions. This patch reverses that precedence, so that users can
> "override" builtin commands. Builtin commands may be accessed by
> issuing the command prefixed by an '@' character.
>
Overriding builtins sounds like a bad idea. For once it creates a
language which is heavily dependent on context. This gets hairy and
messy very fast.
> My motivation for this change is to hook insmod in loaded configfiles
> which set $prefix to a different location than desired. If there are
> any changes needed to help get this functionality included, please let
> me know.
>
Could you detail your usercase more? $prefix is the location where
modules are, why not just set it to right location?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 274 bytes --]
next prev parent reply other threads:[~2014-05-22 7:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 6:37 [PATCH] Allow user-defined functions to override builtins Glenn Washburn
2014-05-19 9:38 ` Michel Hermier
2014-05-19 15:26 ` Ben Hildred
2014-05-22 7:31 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2014-05-24 7:47 ` Glenn Washburn
2014-05-25 3:03 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-05-27 6:27 ` Glenn Washburn
2014-06-02 14:36 ` Andrey Borzenkov
2014-05-25 9:08 ` Michel Hermier
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=537DA7CC.8000507@gmail.com \
--to=phcoder@gmail.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.